Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-27515

Stack trace if push fails - build shows successful but is not (Praqma case 12833)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • pretested-integration-plugin
    • None
    • pretested integration plugin 2.2.1
      Linux Ubuntu 14.04 slave, master Linux Ubuntu 14.04.

      When build is successful, but the push fails the plugin tries to change state of the build to failed. At this point it is not allowed by the Jenkins plugin model.

      So integration is successful according to build status, but the changes never got pushed.

      Performing pre-verified post build steps
[PREINT-GIT] Commiting changes
[PREINT]  git push origin master
[bpe.roadshow.verify] $ git push origin master

Failed to commit integrated changes, message was:
fatal: could not read Username for 'https://github.com': No such device or address

ERROR: Build step failed with exception
java.lang.IllegalStateException: cannot change build result while in POST_PRODUCTION
	at hudson.model.Run.setResult(Run.java:461)
	at org.jenkinsci.plugins.pretestedintegration.PretestedIntegrationPostCheckout.perform(PretestedIntegrationPostCheckout.java:71)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:193)
	at hudson.model.Run.execute(Run.java:1797)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)
Build step 'Pretested Integration post-build' marked build as failure
Finished: SUCCESS

            praqma Praqma Support
            bue Bue Petersen
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: