Migrate jobs to pipeline "in-place"?

We like to migrate some "Free-Style"-projects to pipelines. Is it possible to do this "in place" (i.e. in the same job)? The background is that we do not want to lose the history and links to other jobs. -- You received this message because you are subscribed to the Google Groups "Jenkins Use

Bidirectional SCP-Plugin wanted?

I'm looking for a plugin which can down- and upload files via scp (not only publishing artifact). Any suggestions? -- 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 emai

Re: "mark" and reference artifacts of another build of a job

Ping! Other ideas? -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit http

Re: reference the last build marked as "keep forever"

We do some automatic regression tests for up- and downgrades. And the version marked as "keep forever" ist the reference version for the downgrades. Am Donnerstag, 2. April 2015 08:50:58 UTC+2 schrieb Baptiste Mathus: > > I don't think so. > What's your use case by the way out of curiosity? > -

reference the last build marked as "keep forever"

Is it possible to reference the last build marked as "keep forever" in a similar way than lastSuccessfullBuild? -- 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

Re: "mark" and reference artifacts of another build of a job

In general this plugin can do the work. But it creates real copies in our case (and we talk about a big amount of data) because workspace and build archive reside on different partitions. :( I'm looking more for something like these "lastSuccessfulBuild" links. But it should be possible to cust

"mark" and reference artifacts of another build of a job

We're looking for a solution for the following scenario. One build should be marked e.g. by a manual build parameter. And a later build should have access to the artifacts of the marked build. Until now we've realizied this by filesystem symlinks pointing to the marked builds created as a build

Re: No new jobs are created after upgrading to 1.560 (polling plugin reports no changes when there are)

Am Mittwoch, 23. April 2014 20:32:36 UTC+2 schrieb Michael Beck: > > I had the same issue but found a workaround to fix it for now. I only have > a few jobs so everything runs on my master node. For some reason the jobs > that need to be submitted for polling won't succeed because they don't see

Re: No new jobs are created after upgrading to 1.560 (polling plugin reports no changes when there are)

Same problem here for jobs using Multiple SCMs plugin(0.3) *and *GIT plugin (2.2.1). Jobs using only the GIT plugin work well. -- You received this message because you are s

Trigger on a few git repos, but do not checkout them?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jenkins-community, is it possible to trigger on changes in more than one git repositories, but do not checkout them into the workspace? - -- DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, 10319 Berlin, Germany Tel: +49 30 515932-237 ma

subversion - subtree with fixed revision

ir1/subdirA and source3/dir1/subdirB are 666 and not HEAD. :( Any suggestions? Steffen Sledz -- DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, 10319 Berlin, Germany Tel: +49 30 515932-237 mailto:sl...@dresearch-fe.de Fax: +49 30 515932-299 Geschäftsführer: Dr. Michael Weber, Werner Mög