On Thu, Jan 4, 2018 at 4:53 AM, lucamilanesio wrote:
> I've taken now https://github.com/jenkinsci/pipeline-utility-steps-plugin as
> an example of simple utility steps
Best to start with the official documentation:
I suppose this is an aspect of JENKINS-45245, but if the test actually
runs (as it should in JTH 2.27+), why do you care?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it,
Sharon,
>From context, it sounds like you're using the Job DSL to create Pipeline
jobs. Is that correct?
Could you share an example of what your code would have to look like
without your tool?
Thanks,
-Liam Newman
On Wed, Jan 3, 2018 at 2:09 PM Jesse Glick wrote:
Well, I just do not like red squiggles somewhere in the project. It looks like
a compile error - so if I ignore it now I might ignore some other important red
squiggles in the future...
> Am 05.01.2018 um 01:01 schrieb Jesse Glick :
>
> I suppose this is an aspect of
Initial Jenkins website update, project ideas page and the blog post are
ready for review:
https://github.com/jenkins-infra/jenkins.io/pull/1310
BR, Oleg
четверг, 4 января 2018 г., 0:26:20 UTC+1 пользователь Oleg Nenashev написал:
>
> Hi all,
>
> So we already have a set of project ideas
>
That's correct - we're using Job DSL to create pipeline jobs.
It allows you to set your pipeline job definition as well as the script
portion as part of the same Groovy script using a builder pattern.
The visual editor in Blue Ocean, as far as I know, does not meet our goals
for the main reason
Hey!
I would like to become a mentor. Should I share my ideas on that google
document?
Thanks.
Best Regards,
Anubha
On 15-Dec-2017 8:02 PM, "Oleg Nenashev" wrote:
> Hi all,
>
> I am preparing to the launch of Google Summer of Code 2018
>
I've taken now https://github.com/jenkinsci/pipeline-utility-steps-plugin
as an example of simple utility steps and will add a brand-new
implementation in Java.
On Thursday, January 4, 2018 at 7:57:15 AM UTC, lucamilanesio wrote:
>
> Good point: let me try to see what's the effort for the
Hi all,
It's been more than one month since last message on this thread and we
still don't see any progress to unblock development. I'm sure Jan made a
good job while he was leading the plugin's development and we thank him for
it. Unfortunately he doesn't seem to be active anymore so, can we
If you are using Multibranch, you may be interested in:
https://github.com/jenkinsci/basic-branch-build-strategies-plugin
Checkout the documentation:
https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc
This extension plugin will enable things like:
*
It's all good now, had to upgrade the credentials plugin to a version that
actually used Jenkins.XSTREAM2
On Thu, Jan 4, 2018 at 1:00 PM, Robert Sandell
wrote:
> System credentials seems to be using Jenkins.XSTREAM2 at least
>
System credentials seems to be using Jenkins.XSTREAM2 at least
https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/SystemCredentialsProvider.java#L126
User credentials is "just" stored in a user's properties
Oliver,
Thanks for the release candidate. Is there a docker slim image for the
release candidate testing?
I'm transitioning from testing with a derivative of the Dockerfile as
provided by https://github.com/jenkinsci/docker to using the images
available from
Hello everyone,
Latest LTS RC was made public and it is ready to be tested. Release is
scheduled for 2018-01-17.
Report your findings in this thread or on the test plan wiki page.
Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.89.3/jenkins.war
Check community maintained LTS
On 2018-01-04 15:27, Mark Waite wrote:
Oliver,
Thanks for the release candidate. Is there a docker slim image for the
release candidate testing?
I'm transitioning from testing with a derivative of the Dockerfile as
provided by https://github.com/jenkinsci/docker to using the images
15 matches
Mail list logo