Re: POTD: Jenkinsfile Runner

So the repo has been moved by Kohsuke. Nicolas also reverted the README so it is no longer deprecated. Now we are good, I believe BR, Oleg On Thursday, March 1, 2018 at 8:23:15 PM UTC+1, Kohsuke Kawaguchi wrote: > > Jenkinsfile Runner is an experiment to package Jenkins pipeline execution >

Re: POTD: Jenkinsfile Runner

Le jeu. 4 oct. 2018 à 08:04, Oleg Nenashev a écrit : > Hi Nicolas, > > I am ready to execute on the request. Please confirm that all the data is > backed up in your fork. > Confirmed Please do > > and fork https://github.com/kohsuke/jenkinsfile-runner >>

Re: POTD: Jenkinsfile Runner

Hi Nicolas, I am ready to execute on the request. Please confirm that all the data is backed up in your fork. and fork https://github.com/kohsuke/jenkinsfile-runner > >

Re: POTD: Jenkinsfile Runner

all those changes are related to my version's README.md , no impact on KK's repository Le mar. 2 oct. 2018 à 17:33, Jesse Glick a écrit : > On Tue, Oct 2, 2018 at 10:13 AM

Re: POTD: Jenkinsfile Runner

On Tue, Oct 2, 2018 at 10:13 AM nicolas de loof wrote: > DELETE the jenkinsci/jenkinsfile-runner repository What about https://github.com/ndeloof/jenkinsfile-runner/compare/master...jenkinsci:master ? That should be upstreamed first, no? -- You received this message because you are

Re: POTD: Jenkinsfile Runner

The Jenkins X project is using custom war packager along with https://github.com/kohsuke/jenkinsfile-runner so this get’s a +1 from us. Thanks, James. > On 2 Oct 2018, at 15:13, nicolas de loof wrote: > > > Based on the fact

Re: POTD: Jenkinsfile Runner

Based on the fact custom-war-packager already support KK's approach I'm asking jenkinsci organisation owners to DELETE the jenkinsci/jenkinsfile-runner repository, and fork https://github.com/kohsuke/jenkinsfile-runner as a replacement. My own version

Re: POTD: Jenkinsfile Runner

Oleg, +1 for cleanup, definitely. The path you propose overall sounds good to me. On Thursday, September 6, 2018 at 6:40:23 AM UTC-7, Oleg Nenashev wrote: > > Obviously, step (5) is a bad idea then. Could we just have 2 repos without > "fork" relations then? > If the codebase is not shared,

Re: POTD: Jenkinsfile Runner

Obviously, step (5) is a bad idea then. Could we just have 2 repos without "fork" relations then? If the codebase is not shared, it would help. As you can guess I have my strong opinion about classloader voodoo in KK's > approach to a jenkinsfile-runner CLI. > Fine for PoC IMHO. It improves

Re: POTD: Jenkinsfile Runner

please note ndeloof/jenkinsfile-runner is a complete different design vs KK initial prototype they don't share architecture nor git history (only few java classes) so you'll have to choose one approach over the other As you can guess I have my strong opinion about classloader voodoo in KK's

Re: POTD: Jenkinsfile Runner

+1 for cleaning up. Like we recommend for plugins, it would be nice that canonical repo location is more clearly the one under jenkinsci org Le jeu. 6 sept. 2018 à 15:24, Oleg Nenashev a écrit : > Hi all, > > It seems we have a splitbrain issue in this project. > Currently there is the

Re: POTD: Jenkinsfile Runner

Hi all, It seems we have a splitbrain issue in this project. Currently there is the following fork tree: - https://github.com/kohsuke/jenkinsfile-runner - https://github.com/ndeloof/jenkinsfile-runner - https://github.com/jenkinsci/jenkinsfile-runner Jenkinsfile

Re: POTD: Jenkinsfile Runner

Ouch, that's a shame. It looked like an interesting project, I hope my writing to you didn't trigger that. You say "stress builds and also to burn in our build agents" -- can you elaborate on that? It sounds like you are trying to warm up a cache or something, but I'm not sure what that means in

Re: POTD: Jenkinsfile Runner

Hi, Thomas, Tyler passed me a link to your project https://github.com/tomwillfixit/jenkinless, which is in a similar space with my project of the day called Jenkinsfile Runner. I haven't studied your project carefully yet, but I already see some interesting ingredients like memcached that I have

Re: POTD: Jenkinsfile Runner

On Sat, Mar 24, 2018 at 12:53 PM, wrote: > This might have something to do with this warning, issued right at the start > of the pipeline. > > jenkins.security.ClassFilterImpl#isBlacklisted: rejecting > org.codehaus.groovy.runtime.powerassert.PowerAssertionError

Re: POTD: Jenkinsfile Runner

KK wrote: > I wonder if it'd be nice if Jenkinsfile Runner can do something like the > permissive mode of SELinux, where it runs your pipeline entirely and spit > out the approvals it needed? https://plugins.jenkins.io/permissive-script-security > so instead of invisible WorkflowJob, we create

Re: POTD: Jenkinsfile Runner

It's pretty cool that it actually works, huh? On Mon, Mar 12, 2018 at 10:57 PM Michael Neale wrote: > As an example of how to use (abuse?) this: > > I was able to take a container with the set of "recommended" plugins, and > run it on the "codeship pro" service (which uses

Re: POTD: Jenkinsfile Runner

On Sun, Mar 11, 2018 at 6:43 AM wrote: > From a user perspective, I like your idea of a > "pipeline.sharedlibrary.test" step and/or a "run-pipeline" CLI command. > They would definitely solve configuration issues with plugins, docker, etc. > Now, Jesse mentioned some

Re: POTD: Jenkinsfile Runner

On Wed, Mar 7, 2018 at 1:04 PM Jesse Glick wrote: > On Tue, Mar 6, 2018 at 4:23 PM, Kohsuke Kawaguchi wrote: > > I have another idea. Instead of > > running Jenkinsfile in this CLI and try to emulate your Jenkins instance > as > > closely as possible (in

Re: POTD: Jenkinsfile Runner

Sorry for the bit of delay to come back to this, On Wed, Mar 7, 2018 at 5:46 AM Bill Dennis wrote: > Kohsuke - some more answers to your questions inline below. > > Also I thought of these other things on my walk to the office this morning > that might be of interest: >

Re: POTD: Jenkinsfile Runner

As an example of how to use (abuse?) this: I was able to take a container with the set of "recommended" plugins, and run it on the "codeship pro" service (which uses docker): https://github.com/michaelneale/codeship-jenkinsfile On Friday, March 2, 2018 at 6:23:15 AM UTC+11, Kohsuke

Re: POTD: Jenkinsfile Runner

>From a user perspective, I like your idea of a "pipeline.sharedlibrary.test" step and/or a "run-pipeline" CLI command. They would definitely solve configuration issues with plugins, docker, etc. Now, Jesse mentioned some implementation challenges in his post from Wed, 07 Mar 2018 13:04:46

Re: POTD: Jenkinsfile Runner

On Tue, Mar 6, 2018 at 4:23 PM, Kohsuke Kawaguchi wrote: > I have another idea. Instead of > running Jenkinsfile in this CLI and try to emulate your Jenkins instance as > closely as possible (in terms of configuration), we could just run > Jenkinsfile in the current Jenkins, in

Re: POTD: Jenkinsfile Runner

Kohsuke - some more answers to your questions inline below. Also I thought of these other things on my walk to the office this morning that might be of interest: - Parameters to jobs : most of my pipeline jobs have parameters defined inside. Would the Jenkinsfile Runner have a way to pass in

Re: POTD: Jenkinsfile Runner

On Tue, Mar 6, 2018 at 2:57 AM Bill Dennis wrote: > Thanks Kohsuke, I tried to give some answers to your questions inline > below, if I didn't mess up the reply.. > > Bill > > On Friday, 2 March 2018 17:57:24 UTC, Kohsuke Kawaguchi wrote: > >> >> >> On Fri, Mar 2, 2018 at

Re: POTD: Jenkinsfile Runner

Oleg gave us the fix, which I merged to the master just now. I think that'll fix the problem. On Tue, Mar 6, 2018 at 1:22 AM Michael Neale wrote: > Trying this out, looks like I am hitting JEP-200: > > https://jenkins.io/redirect/class-filter/ > > Need to dig in further (I

Re: POTD: Jenkinsfile Runner

On Sun, Mar 4, 2018 at 8:13 AM wrote: > I think Jenkinsfile Runner brings a lot of opportunities for pipeline > developers. The most obvious ones to me are > >1. Pipeline development (Jenkinsfile) >2. Shared library development > > *Pipeline development* > >

Re: POTD: Jenkinsfile Runner

Yeah, there are many possible ways to go about something like this, including what you described. That's why I'm trying to hear from Bill what his world looks like. I can use some concrete data points like that. On Fri, Mar 2, 2018 at 11:08 AM Jesse Glick wrote: > On Fri,

Re: POTD: Jenkinsfile Runner

https://github.com/kohsuke/jenkinsfile-runner/pull/8 On Tue, Mar 6, 2018 at 8:13 PM, Oleg Nenashev wrote: > I will create a pull request, stay tuned > > On Tuesday, March 6, 2018 at 7:32:21 PM UTC+1, joha...@schnatterer.info > wrote: >> >> Same exception here:

Re: POTD: Jenkinsfile Runner

I will create a pull request, stay tuned On Tuesday, March 6, 2018 at 7:32:21 PM UTC+1, joha...@schnatterer.info wrote: > > Same exception here: java.lang.UnsupportedOperationException: Refusing to > marshal io.jenkins.jenkinsfile.runner.SetJenkinsfileLocation for security > reasons; > > I

Re: POTD: Jenkinsfile Runner

Same exception here: java.lang.UnsupportedOperationException: Refusing to marshal io.jenkins.jenkinsfile.runner.SetJenkinsfileLocation for security reasons; I created an issue with full stacktrace . Jesse or Oleg, maybe you could

Re: POTD: Jenkinsfile Runner

Yeah, the entire library needs to me whitelisted (or packaged as Jenkins module). It's actually a quick-win to get it fixed as long as it is a development tool. BR, Oleg On Tue, Mar 6, 2018 at 5:00 PM, Bill Dennis wrote: > I too am seeing the JEP-200 issue with these

Re: POTD: Jenkinsfile Runner

I too am seeing the JEP-200 issue with these exceptions packaging to a Docker image and running with that using Docker for Windows: java.lang.UnsupportedOperationException: Refusing to marshal io.jenkins. jenkinsfile.runner.FileSystemSCM for security reasons; see https:

Re: POTD: Jenkinsfile Runner

On Tue, Mar 6, 2018 at 4:22 AM, Michael Neale wrote: > java.lang.UnsupportedOperationException: Refusing to marshal > io.jenkins.jenkinsfile.runner.SetJenkinsfileLocation for security reasons; > see https://jenkins.io/redirect/class-filter/ As suggested in that link, the

Re: POTD: Jenkinsfile Runner

Thanks Kohsuke, I tried to give some answers to your questions inline below, if I didn't mess up the reply.. Bill On Friday, 2 March 2018 17:57:24 UTC, Kohsuke Kawaguchi wrote: > > > > On Fri, Mar 2, 2018 at 9:26 AM Bill Dennis > wrote: > >> Hello Kohsuke - >> >> I am a

Re: POTD: Jenkinsfile Runner

I think Jenkinsfile Runner brings a lot of opportunities for pipeline developers. The most obvious ones to me are 1. Pipeline development (Jenkinsfile) 2. Shared library development *Pipeline development* Right now (as described by others in this thread) pipeline development is either a

Re: POTD: Jenkinsfile Runner

On Fri, Mar 2, 2018 at 12:56 PM, Kohsuke Kawaguchi wrote: > well, though. Can you tell me more about this? I'm imagining you'd want to > be able to selectively mock out some steps (e.g., when Jenkinsfile gets to > sh "./deploy.sh" don't actually do it and pretend that it

Re: POTD: Jenkinsfile Runner

On Fri, Mar 2, 2018 at 9:26 AM Bill Dennis wrote: > Hello Kohsuke - > > I am a developer using Jenkins pipeline quite lot where I work. > > We are using Jenkins pipelines in two scenarios: > >- For CI building and testing some of our internal components (what >

Re: POTD: Jenkinsfile Runner

Hello Kohsuke - I am a developer using Jenkins pipeline quite lot where I work. We are using Jenkins pipelines in two scenarios: - For CI building and testing some of our internal components (what Jenkins is traditionally used for) - For running / orchestrating complex automation

Re: POTD: Jenkinsfile Runner

For the third use case, what might be useful is an archetype or two analogous to https://github.com/jenkinsci/archetypes/tree/master/scripted-pipeline/src/main/resources/archetype-resources

Re: POTD: Jenkinsfile Runner

And of course I forgot to have the link to the project! https://github.com/kohsuke/jenkinsfile-runner On Thu, Mar 1, 2018 at 11:22 AM Kohsuke Kawaguchi wrote: > Jenkinsfile Runner is an experiment to package Jenkins pipeline execution > as a command line tool. The intend use

POTD: Jenkinsfile Runner

Jenkinsfile Runner is an experiment to package Jenkins pipeline execution as a command line tool. The intend use cases include: - Use Jenkins in Function-as-a-Service context - Assist editing Jenkinsfile locally - Integration test shared libraries Over the past year, I've done some