Home
TeamCity Support | JetBrains
Contact Support
Community
Sign in

Gormanst

Avatar
  • Total activity 10
  • Last activity February 27, 2017 20:37
  • Member since January 11, 2017 17:26
  • Following 0 users
  • Followed by 0 users
  • Votes 0
  • Subscriptions 3
Activity overview Posts (3) Comments (4)
Sort by recent activity Recent activity Votes
  • Created February 27, 2017 20:37
    Thanks for the answer but the question was many days ago. I couldn't figure out what the problem was so I nuked the instance in AWS and spawned a new one, the problem went away.
    1. Community
    2. TeamCity General Topics
    3. AWS EC2 Linux AMI buildAgent permission denied
    • 0 votes
  • Created January 17, 2017 14:03
    It is the "exposes its repository" part I don't understand. Is there some way the TeamCity can allow me to expose a repository or are suggesting something simpler like NFS sharing a .m2 folder?   
    1. Community
    2. TeamCity General Topics
    3. Maven multi module and remote buildAgent
    • 0 votes
  • Created January 17, 2017 13:53
    "exposes its repository through an agent requirement"   I am searching for this now trying to figure out how to do expose the repo? Can you give me a pointer to how I expose the repo?
    1. Community
    2. TeamCity General Topics
    3. Maven multi module and remote buildAgent
    • 0 votes
  • Edited January 12, 2017 13:27
    Thank you so very much for this direction. Perfect answer and much needed help. Plus, it helps give a little confidence in that we are doing it right.    
    1. Community
    2. TeamCity General Topics
    3. Multi Module Maven simultaneous build steps
    • 0 votes
Copyright © 2000– JetBrains s.r.o.