Thank you Sam, Will take a shot on this and get back. On Monday, 31 July 2017 14:24:44 UTC-7, Sam K wrote: > > Hi > > I'm not saying this is the best way... > > You can add the feature to kick off jobs remotely using a token. Then > you can somehow grab the parameters of the job. For example, if user > clicks on job no. 6, then this URL gives you the parameters. With > wget/curl magic, I'm sure you can get all the parameters. > > http://<jenkins-url>/job/Job-1/6/parameters/ > > Then you can use the URL pattern below to kick off another job with the > parameters gathered above > > > http://<jenkins-url>/job/myjob/buildWithParameters?token=TOKEN&PARAMETER=Value > > > > > On Sunday, July 30, 2017 at 11:18:58 AM UTC-7, Deepu Sundar wrote: > > Hi Team, >> >> Need your expert advice on the below query, appreciate your help. >> >> We have a Jenkins CI/CD process in place for deploying AWS lambda >> functions into cloud and it is fully automated. >> >> Now we are building a service portal to manage all aspects of the >> services being deployed. One of the UI of the portal is deployment history >> page which will list out all the current and past build history (may be >> similar to jenkins shows the build history) >> >> From the UI, the user should be able to trigger the build again (like >> redeploying a previous version = run a previous build with same exact >> configuration). What is best way to do this? What are metadata Jenkins may >> require to run a previous build with same exact configuration? What >> Jenkins API we can use for this purpose. >> >> Thanks! >> >> regards, >> Deepu >> >
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/574d754d-fd6b-432a-936b-30aeb28cdb5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
