Issue Type: Bug Bug
Affects Versions: current
Assignee: redsolo
Components: tfs
Created: 29/Jul/14 1:55 PM
Description:

Configured TFS Plugin to use update only

  • Build Step 1: Execute Shell (Print out TFS_CHANGESET)
  • Build Step 2: Execute Maven Build (Maven 3.1.1)
  • Build Step 3: Execute Shell (rolling_label.sh ${WORKSPACE} ${BUILD_NUMBER} ${TFS_CHANGESET})

The execution build step Nr. 3 fails from time to time by the cause that the TFS_CHANGESET variable has not been set which can't be cause within the build step 1 it will be correctly printed out to the jenkins console.

The following is the output in case of a failure:

[portal-HEAD] $ /usr/bin/bash -xe /temp/hudson1539801749356572417.sh
+ /build/label.sh /opt/build/xxxxx-HEAD 4855

The following is the output in case of success:

[Current build status] check if current [SUCCESS] is worse or equals then [SUCCESS] and better or equals then [SUCCESS]
Run condition [Current build status] enabling perform for step [Execute shell]
[xxxx-HEAD] $ /usr/bin/bash -xe /temp/hudson3621978596655594520.sh
[WARNINGS] Parsing warnings in console log with parser Maven
Email was triggered for: Success

which shows that only the TFS_CHANGESET is not being set.

Environment: Currently running a build in Jenkins (1.546) using the TFS Plugin 3.1.1.
Project: Jenkins
Priority: Blocker Blocker
Reporter: Karl-Heinz Marbaise
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to