Snapshot Dependency Not Executing SSH Exec
I have a project with two Build Steps. Step A builds the jar and deploys it to Nexus. Step B contains a Snapshot Dependency upon A and executes an SSH Exec step to deploy the jar to the appropriate environment from Nexus.
I have added a 'Finish Build Trigger' to Step B which points to Step A. I am limiting the branches to those not in master. I do not want to ever deploy from master in this project
| Parameters Description | ||
|---|---|---|
|
Finish Build Trigger
|
Wait for a successful build in: Porter Standalone - Snapshot / Build and Deploy to Nexus Branch filter: +:/refs/heads/* -:/refs/heads/master
|
|
My "Finish Build Trigger" with a Snapshot Dependency never executes. The Build Chain for this projects shows 1 Successful Build (Step A) and 1 Pending Build (Step B). Nothing seems to move Step B from Pending.
What have I configured incorrectly?
Please sign in to leave a comment.
Hello Jadams
I think you have set all things properly but can you please provide the logs of build so we can verify why your step B is getting stuck while build?
Best Regards,
Vishal Ahir.
Hi,
Thanks for trying to help, Vishal, but as of now logs don't seem to be necessary
@jadams: First of all, I wanted to ask you to try and follow our terminology when posting here. While it's understandable, build steps are a very specific thing in teamcity, and taking your message literally it doesn't really make any sense. I'm assuming that what you call "steps" are actually build configurations.
If B is pending, it might be pending triggering or pending because it's on the build queue. It would be important to check this. If A was run and B weren't expected to trigger it wouldn't show as "pending".
Can you confirm exactly which state it's in, and see if it tells you a reason why it's not being run?
1. Your UI is conflicting. It is both "Build Steps" and "Build Configurations". Be consistent:
2. It is Pending but not Queued. The only way I was able to determine that it is Pending is by looking at the Build Chains. I haven't been able to see any other information .The Build Log includes nothing concerning the second build in the chain. See the pointer and mouse over popup:
1- It's not build configurations and build steps, the UI is not conflicting, at least not in that regard. You are showing the different build configurations of your project, and that column shows the different build steps each build configuration has. A single build configuration can have multiple build steps and in that case it would be listed there, such as what can be seen here:
More info on configurations: https://www.jetbrains.com/help/teamcity/build-configuration.html
More info on steps: https://www.jetbrains.com/help/teamcity/configuring-build-steps.html
2- Thanks for clarifying. As we weren't on the same page terminology-wise I thought it would be better to do so first. In this case, the second build has not triggered at all and thus is "pending" for the chain, but not triggered. You could manually run it from that same page to complete that chain, but it seems like the finish build trigger is not working. From the screenshot, I think that the issue is that you are using "+:refs/heads/*" and "-:refs/heads/master", but you are already cutting the name in the branch specification, as you see, the branch name is displayed as "teamcity", not as "refs/heads/teamcity". You can try to remove the "refs/heads/" from the branch filters in the trigger and that would probably do the trick. Leave it like "+:*", "-:master" instead.
If it doesn't work, could you please share a screenshot with the finish build trigger configuration?