stash triggering bamboo build problems after https switch

Robert Cordeau

Hi,

I'm running the 5.7.2 Bamboo and stash 3.6, and everything was working great with Stash triggering builds in Bamboo on check in.  But, I recently turned on SSL on the Tomcat servers for all of the Atlassian products we have, and Stash triggered builds don't work anymore.  I can poll fine, but what used to work now does not.  I have turned on logging but I don't see any obvious errors that would point me in the right direction.  Anyone have any ideas?

 

Thanks,

Rob

rsperafico

Hello Robert,

Thank you for your question.

As Daniel Wester have mentioned, it is most likely the protocol change has not being update in the application links and due to that, the requests are not going through.

I would suggest you on:

In order to create the application links, you should be using the URL used to hit the application (Stash, Bamboo) in your web browser.
Please, notice the very same URL should be the one set up as Base URL within the Application.

   When using Bamboo 5.6+ and Stash 3.2+ newly created application link with default settings:

• The servers have the same set of users and usernames disabled
• I am an administrator on both instances enabled
  
  will result in application link created with:
• Trusted Apps authentication disabled
• OAuth authentication enabled:
  • Allow 2-Legged OAuth enabled
  • Allow user impersonation through 2-Legged OAuth disabled
• Basic Auth authentication disabled

In Stash, please make sure you have "Stash administration >> Settings >> Server Settings >> SSH access" configured as per following:

[x] SSH enabled
[x] SSH access keys enabled
SSH Port: 7999

In Bamboo, please do not forget to Define a new version control capability.

1. please, run SSLPoke from Bamboo box against Stash box and vice-versa

   # from Stash box
   root@hostname:~$ java SSLPoke bamboo.base.url 443
   Successfully connected
    
   # from Bamboo box
   root@hostname:~$ java SSLPoke stash.base.url 443
   Successfully connected

2. please, remove and recreate the application link between Bamboo and Stash

3. enable debug logging in Stash by going to the Stash admin area, choose Logging and Profiling (under 'Support') and select Enable debug logging.

4. enable debugging information by adding the following under "Bamboo administration >> System >> Log settings >> Classpath"

   com.atlassian.bamboo.plan.branch,  type: ALL
   com.atlassian.bamboo.build.strategy,  type: DEBUG 
   com.atlassian.bamboo.plugins.stash.events, type: DEBUG

   update the log level to "DEBUG" on the following:

   com.atlassian.bamboo.plugins.ssh,     type: WARN
   com.atlassian.bamboo.ssh,     type: WARN

   and add the following:

   com.atlassian.bamboo.plugins.git.GitRepository,      type: DEBUG

5. go to your repository settings in Bamboo and hit Save

6. run a new build

The above will help you on troubleshooting 

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

—

Kind regards,
Rafael P. Sperafico
Atlassian Support