Jump to content

problems with bamboo intgration


Paco1863

Recommended Posts

Here goes,

Bamboo creates 2 build-dir

the first has the name of the project while the second has the name of the project+the job.

When I select PlasticSCM for the project the plastic.selector is as expected

repository "Phoenix"

path "/"

branch "/main/development"

checkout "/main/development"

but the plastic.selector in the project+the job directory (which is used in the build) has the default selector

repository "default"

path "/"

branch "/main"

checkout "/main"

which of course in my scenario doesn't exist.

I have checked my settings in Bamboo and verified that the job is to use the project version control settings. I have also set the version control settings for the job to

repository "Phoenix"

path "/"

branch "/main/development"

checkout "/main/development"

But no change, the selector is always set to the default in the job directory and the build fails because the project is not being checked out.

Don't know what to look at next ](*,)

Any help/ideas would be appreciated.

Thanks

Bob

Link to comment
Share on other sites

  • 4 weeks later...

The new Bamboo plugin have been reviewed, fixed a couple of things and released in the current latest 3.0.187.26 :), go download it from: https://www.plasticscm.com/download/editions.en.aspx

Also, a KB article is published at our info center:http://www.plasticscm.com/infocenter/technical-articles/kb-how-to-configure-plastic-scm-with-atlassian-bamboo.aspx

Also, hold an eye at the announcements in this forum.

regards,

Miller

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...