Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If splitting the job into 2 jobs is not an option, you may consider<br> <a href="https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin" rel="nofollow">https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin</a><br> (this is pre-installed with Jenkins I believe). This will make the "promotion" steps a separate and repeatable process. You can configure it to run automatically after build, and then manually on demand when needed. </p> <p>If your post-build steps require access to build artifacts, you will need to use <a href="https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin" rel="nofollow">https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin</a> to copy the build artifacts to the promotion's workspace.</p> <p>Another solution is to <strong>skip build step</strong> based on parameter. Have a <strong>Choice</strong> parameter called <em>SkipBuild</em> or something. Set the possible values to TRUE/FALSE, default to FALSE</p> <p>In your <strong>Build</strong> step, before actually building, check if <em>SkipBuild</em> is set to TRUE. If TRUE, exit 0, if FALSE (which is default) then run build command.</p> <p>This way, automatic Build executions will always run the Build step. But you can also manually run the build and select "SkipBuild=TRUE" to skip the build step and go straight to post-build actions. If you need to skip some post-build actions, you would need to implement this <em>SkipBuild</em> parameter there as well.</p> <p>Careful however as subsequent executions of the build, even with "SkipBuild=TRUE" will still perform an SVN checkout, so your workspace may change.</p>
    singulars
    1. This table or related slice is empty.
    1. POJenkins - How to run post-build action without re-running the job?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSlav
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you explain how the `Promoted Builds` plugin works without having multiple jobs? The documentation only mentions _automatic_ promotion when trigged by another job.
      singulars
      1. PO
      1. USCraig
    2. CO`Promoted Builds` allows to execute actions on existing past builds. It does retain some information from the past build, such as `$PROMOTED_NUMBER` which indicates which previous build the promotion is running on. However, you still need to use `Copy Artifact Plugin` to access the artifacts from the previous builds. There isn't enough space in comments to explain it, but in short the "promotion" allows you to run pretty much any build and post-build action as you normally would. If you don't want it to be triggered automatically, you can set it `Only when manually approved`
      singulars
      1. PO
      1. USSlav
    3. COI have a lengthy explanation on how to archive artifacts here: http://stackoverflow.com/questions/15140580/jenkins-continuous-delivery-with-shared-workspace and another lengthy explanation on the promotions here http://stackoverflow.com/questions/15126059/how-to-promote-a-specific-build-number-from-another-job-in-jenkins . In your case, read how the `deploy job` uses `copy artifacts plugin` and actually do that as your first build step in the promotion job. Then, as a second build step, execute your static analysis
      singulars
      1. PO
      1. USSlav
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload