Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>One mechanism to deploy off of a build on Jenkins is to use artifacts to place the latest binary in a known location, and then kick off a new job (only on success of the compile/test phase) which uses (private key protected) ssh or scp to copy the artifacts to the test/production machine and then perform the install.</p> <p>We use a similar mechanism for some automated testing that we do. The tricky part is getting the shell command to handle the ssh keys, so we do the following:</p> <pre><code>eval `ssh-agent -s` ssh-add ~/.ssh/your_private_key_here </code></pre> <p>As long as that private key is on the Jenkins server and the public key is on the server you're trying to push to, you can then use <code>ssh</code> and <code>scp</code> commands in the rest of the script to perform functions on the server in question.</p> <p>If you prefer to run the process entirely from the target server end, you can create a small script that runs on the server that checks for new files in the artifact directory of your Jenkins server build. Thanks to the <code>latest</code> path, you don't have to know the build number to do this. To find the specific path, you can log in to your Jenkins server (once you've saved at least one artifact), and find the project you are using and look at the <em>Last Successful Artifacts</em>, which will be URLs to the last successful builds of the artifacts. These URLs remain constant and always point at the most recent successful build, so you don't have to worry about them changing unless the project name or server name changes.</p> <p><strong>NOTE</strong>: there are security holes here that you can drive a truck through if you are doing this for anything other than a deployment to test. In the case of the first mechanism, your build server has an <code>ssh</code> key that gives it access (potentially destructive) to the target. In the case of the second mechanism, you are trusting that the Jenkins server will only serve up binaries that are good for you. However, for test environments, push to stage, etc. these techniques will work well.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow could I automate build deploy in jenkins?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USgaige
    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. This table or related slice is empty.
    1. COThanks a lot for the response... I have few clarification in this... We used to do deployment testing as well [tats the reason we use the released build number] So in this case it will copy the files and not deploy it actually.So there any way to deploy it using jenkins by the build number? Sorry if my understanding is not correct...
      singulars
      1. PO
      1. USSujith
    2. CO@Sujith I don't think I'm following you precisely. The deployment is going to have to be done within the `ssh` script, since there's no predefined mechanism in Jenkins to deploy arbitrary packages to another server. But, I'm not sure if that's the question you have. If you want to manually deploy, you can set up a Project that requires manual triggering. If you wanted to carry the build number along with, you can use the build number as a variable in the script to pass that along in your `ssh` command. Can you clarify what you want done with the build number?
      singulars
      1. PO
      1. USgaige
 

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