Re: [GSoC 2018] - Preliminary announcement

[Anubha Maneshwar]

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
>  in the Jenkins project.
> As in 2016/2017, we will be looking for mentors
> . It is
> critical to have a diverse number of proposal so that the Jenkins Project
> could get accepted this year, so I want to start it early this year.
>
> GSoC is a pretty big deal for mentors (several hours per week), but it is
> possible to get a full-time student working on your project for almost 4
> months. Mentorship does not require deep knowledge of Jenkins development
> itself, because there will be advisors around. So any contributor can
> participate if he has interest in it and opportunity to dedicate enough
> time.
>
> Would somebody be interested to be a mentor? If yes, just respond to this
> thread.
>
> -
>
> Useful links:
>
>- GSoC 2018 timeline
>
>- GSoC 2017 announcement with details
>
>- GSoC 2016 project idea examples
>
>- GSoC Mentor Guide 
>
> More documentation will be published this month if there is an interest in
> the community.
>
> Best regards,
> Oleg
>
> --
> 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, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/78c7fe1d-1a11-4980-abd2-92a0e2f81cd2%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAOSC8jgt%2BsQL3z5jYSZ9_XDqvQzB5nUGfRVXOV9Z4ysX5ex37w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin idea - declarative pipeline script builder

[Sharon Grubner]

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 that we set up all of our jobs using DSL. In addition, 
as part of our DSL libraries we like to set up different utilities that 
lead to more consistent pipeline jobs across our different projects/users. 
I believe the visual editor would not help us achieve this goal.

Here's another simplified example of how you would you this script builder, 
compared to what it would look like without it.
Without it:
pipelineJob('example'){
definition {
cps{
script("""pipeline {
agent none
stages {
stage('Stage 1') {
stage('Build Stage') {
agent {
node {
label 'windowsBuilderServer'
}
}
steps {
checkout([$class: 'GitSCM', branches: [[name: env.ghprbActualCommit]], 
browser: [$class: 'GithubWeb', repoUrl: "XX"], 
doGenerateSubmoduleConfigurations: false, poll: false, extensions: [], 
submoduleCfg: [], userRemoteConfigs: [[credentialsId: "YY", url: 
"XX.git"]]])
stash includes:"ProjectName/**/*", name:"stash1"

}
post {
always {
deleteDir()
}
}
}
}
stage('Stage 2') {
parallel {
stage('Parallel 1') {
agent {
node {
label 'linuxBuildServer'
}
}
steps {
deleteDir()
unstash name:"stash1"
sh """some script"""
}
post {
success {
deleteDir()
}
always {
archiveArtifacts artifacts:"*.e*,*.o*", excludes:"", 
allowEmptyArchive:true, fingerprint:true, onlyIfSuccessful:false
junit allowEmptyResults: true, testDataPublishers: [[$class: 
'AttachmentPublisher'], [$class: 'StabilityTestDataPublisher']], 
testResults: 'test_results/*.xml'
}
}
}
}
}
}
}
""")
sandbox()
}
}



And using the script builder: **Contains a couple of our internal helper 
methods but they don't have anything fancy
Stage stage1 = Stage.create('Stage 1')
.setAgent(Agent.fromExecutor(Executor.WINDOWS))
.addStep(checkoutFromGit('XX', 'env.ghprbActualCommit'))
.addStep(stash('stash1', 'ProjectName/**/*'))
.addPost(Post.Condition.ALWAYS, deleteDir())
ParallelStage stage2 = ParallelStage.create('Stage 2')

//datasetList is a List such that each string is a data set name
//The following will create a prallel stage for each list element
datasetList.collect { 
Stage.create(it)
.setAgent(Agent.fromExecutor(Executor.LINUX))
.addStep(deleteDir())
.addStep(unstash('stash1'))
.addStep(sh("""some script"""))
.addPost(Post.Condition.SUCCESS, deleteDir())
.addPost(Post.Condition.ALWAYS, 
archiveArtifacts('*.e*,*.o*','',true, true,false))
.addPost(Post.Condition.ALWAYS, 
publishJUnitXml('test_results/*.xml', true))
}.each { stage2 = stage2.addStage(it) }

def script = PipelineScript.create()
.addStage(stage1)
.addParallelStage(stage2)


pipelineJob('example'){
definition {
cps{
script(script)
sandbox()
}
}


As you can see you could set up the entire job in a single block (as shown 
in my first post) or break the definitions to multiple variables for more 
complex logic.
I simplified most of the above example since it heavily depends on our 
utilities libraries but hopefully it is sufficiently clear.


This library has been widely used in our team and received positive 
feedback so I thought it would be useful to share with the community. It is 
definitely not the only way of doing things but we found it to be pretty 
useful.

Sharon


On Thursday, January 4, 2018 at 3:13:15 PM UTC-8, Liam Newman wrote:
>
> 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:
>
>> On Wed, Jan 3, 2018 at 1:50 PM, Sharon Grubner > > wrote:
>> > requires all users to know the
>> > declarative pipeline syntax
>>
>> Why not just use the Declarative visual editor in Blue Ocean, for
>> users unfamiliar with the syntax?
>>
>> > does not allow sharing common functions and
>> > practices.
>>
>> You can use Groovy libraries from Declarative, with certain restrictions.
>>
>> I am not sure I see the point here. If you want to expose a
>> programmatic interface to users, then why are you using Declarative at
>> all? You can publish libraries for use from Scripted which offer
>> reusable functional chunks of all kinds already (including
>> “higher-order” functions such as control operators), and this would be
>> much more direct as your script would be the Groovy that actually
>> runs, rather than a builder that creates a script that is interpreted
>> by Declarative to create something to run. Maybe I am just not
>> following what your tool actually does.

Re: org.jenkins-ci.main:jenkins-war:executable-war:2.73.3 cannot be resolved (Was: Re: Issue with upgrading to Jenkins 2.76)

[Ullrich Hafner]

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 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, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr03rtCV-ab%3DCOkjg-jdk12KxGQPoCuw%2BBMJHZJtfq%3Di0g%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/C53B64C7-F7DA-4442-ACD0-83EF83C0EE15%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: [GSoC 2018] - Preliminary announcement

[Oleg Nenashev]

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 
> ,
>  
> but we have only 3 potential mentors who stepped forward. IMHO it is not 
> enough to be accepted to GSoC, so in the current state we will unlikely 
> apply.
>
> We will review the ideas status at the next Governance meeting on Jan 17 
>  and 
> decide whether it makes sense to apply (application deadline is Jan 23). If 
> somebody is interested to be a mentor, please do not hesitate to respond to 
> this thread or reach out to me privately if needed.
>
> Best regards,
> Oleg
>
>
> вторник, 19 декабря 2017 г., 12:02:42 UTC+1 пользователь Oleg Nenashev 
> написал:
>>
>> Hi,
>>
>> I suggest discussing the ideas in a Google Doc.
>> Wiki is fine, but it is complicated to handle the feedback there.
>> I have started 
>> https://docs.google.com/document/d/1q2p_XZEdbkcVDMpEPTtjPS15i2Oq3CQgH_geJjPhofY/edit?usp=sharing
>>  
>> for now, so please feel free to propose your project ideas there.
>>
>> Once the ideas are finalized, I will be moving them to the jenkins.io 
>> website.
>>
>> BR, Oleg
>>
>>
>>
>> понедельник, 18 декабря 2017 г., 9:18:13 UTC+1 пользователь Ewelina 
>> Wilkosz написал:
>>>
>>> Count me in, for Jenkins Configuration as Code
>>>
>>> On Saturday, December 16, 2017 at 5:50:19 PM UTC+1, martinda wrote:

 I would like to renew this experience. You can count me in as a mentor.

 Where should we propose and discuss project ideas? I suggest a page on 
 the Wiki like GSoC 2016 project idea examples 
 .
 I have a few ideas already:

- Improvements to workspace data retention feature (aka automatic 
workspace clean up)
   - Erase  builds older than X days of builds but always keep the 
   last Y builds regardless of how old the builds are
   - Erase the external workspaces 
    in 
   accordance with the workspace retention policy
   - Summary Report plugin 
 workflow compatibility
- Speed improvements to the ATH (like use a dockerized jenkins 
instead of restarting jenkins for every test, but I am sure there are 
 many 
ideas here)

 Martin

>>>

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6aafc8d2-e8c8-40d0-b052-a00425f18f1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

[Jesse Glick]

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:

https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1sNtVakNOrB-wqLYPW1AjSsEjBYABC0u3TkqUxNXtg0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: org.jenkins-ci.main:jenkins-war:executable-war:2.73.3 cannot be resolved (Was: Re: Issue with upgrading to Jenkins 2.76)

[Jesse Glick]

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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr03rtCV-ab%3DCOkjg-jdk12KxGQPoCuw%2BBMJHZJtfq%3Di0g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin idea - declarative pipeline script builder

[Liam Newman]

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:

> On Wed, Jan 3, 2018 at 1:50 PM, Sharon Grubner 
> wrote:
> > requires all users to know the
> > declarative pipeline syntax
>
> Why not just use the Declarative visual editor in Blue Ocean, for
> users unfamiliar with the syntax?
>
> > does not allow sharing common functions and
> > practices.
>
> You can use Groovy libraries from Declarative, with certain restrictions.
>
> I am not sure I see the point here. If you want to expose a
> programmatic interface to users, then why are you using Declarative at
> all? You can publish libraries for use from Scripted which offer
> reusable functional chunks of all kinds already (including
> “higher-order” functions such as control operators), and this would be
> much more direct as your script would be the Groovy that actually
> runs, rather than a builder that creates a script that is interpreted
> by Declarative to create something to run. Maybe I am just not
> following what your tool actually does.
>
> --
> 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, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1_KFxTjnEiddcwZv%3D7jndJvgX%2BgRp%3DUL5DeB5bmx%2B7%3Dg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAA0qCNyZGYN5Lmhp8uZh6%3DQjuDd-p0sDz2fWfXUvEzB6fnyPjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Asking for commiter access to amazon-ecs-plugin

[Jordi Miguel]

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 give 
commit permissions to someone who's active? On previous messages looks like 
Douglas Manley was happy to take over the role and I suspect he has not 
changed his mind.
I don't care much who ends up being the new maintainer but we're 
approaching the year mark since the last commit that found its way to 
master's branch and there are plenty of PR's waiting for a merge that 
haven't succeed because we don't have anyone with write permissions in the 
active community.

I hope we can find a solution to this issue soon. If there is anything I 
can do to help resolve problems please don't hesitate to ask.


Thanks,
Jordi

El miércoles, 29 de noviembre de 2017, 21:39:40 (UTC+1), Yaramada Surya tej 
escribió:
>
> Hi Mathus,
>   It would be great if any one can change the maintainer 
> of this plugin to Douglas as he is willing to took it so that we can 
> utilize this plugin , many of us are waiting to get this pull request 
> merged.
>
>
> Thanks
> Surya
>
> On Thursday, 7 September 2017 17:33:57 UTC-4, Baptiste Mathus wrote:
>>
>> Hello,
>> Seems like Jan is not active either these days or anymore at all.
>>
>> So either you can see if you want to adopt this plugin (in that case 
>> please follow the process described on the wiki), or this is likely to stay 
>> this way until someone does I suspect.
>>
>> Baptiste
>>
>> Le 7 sept. 2017 17:22, "Surya yaramada`"  a écrit :
>>
>>> Hi,
>>>  I am sorry for interrupting again but can I please know if there is 
>>> a chance to merge the pull requests for AMAZON-ECS plugin.
>>>
>>>
>>> Thanks 
>>> Surya
>>>
>>> On Thursday, August 24, 2017 at 4:12:47 PM UTC-4, Daniel Beck wrote:


 > On 24. Aug 2017, at 22:09, Surya yaramada`  
 wrote: 
 > 
 >  Can I get any updates on this? 
 > 

 There's no need for multiple emails per day. Give him a week or so. Jan 
 may well be on vacation. 

 -- 
>>> 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, send 
>>> an email to jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/4f569b34-cfb3-427f-adc3-40406f9c6b3e%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d4e56d13-fe7b-4d43-a489-8fe2f7f83d8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.89.3 LTS RC testing started

[Oliver Gondža]

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 
available from https://hub.docker.com/r/jenkins/jenkins/ as the base 
image.  Unfortunately, I don't see a tag for the release candidate.


Is that intentional?

If that's intentional, I'll test the release candidate with my 
Dockerfile derivative technique rather than using official images as the 
base image.


There are no LTS RC docker images generated at the moment. It would be 
great if we can provide users some reusing the image building infra we 
use for releases, but I never gave it a try.


--
oliver

--
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/748593b2-aaaf-520c-4447-4d192c0a3597%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.89.3 LTS RC testing started

[Mark Waite]

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 https://hub.docker.com/r/jenkins/jenkins/ as the base
image.  Unfortunately, I don't see a tag for the release candidate.

Is that intentional?

If that's intentional, I'll test the release candidate with my Dockerfile
derivative technique rather than using official images as the base image.

Thanks,
Mark Waite

On Thu, Jan 4, 2018 at 1:12 AM Oliver Gondža  wrote:

> 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 test plan
> https://wiki.jenkins-ci.org/display/JENKINS/LTS+2.89.x+RC+Testing
>
> Thanks
> --
> oliver
>
> --
> 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, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3b6fecba-63e5-abfe-1225-4969e0ffc55d%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEQ0XzfhrKHdJndoRsHADycn0FRzLqtekyTm%3DLv31oo8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Basic Branch Build Strategies plugin

[Stephen Connolly]

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:

* Not rebuilding PRs if only the target branch changed

* Automatically building tags that were "created" within a specific time
window

If somebody wants to take their hand at implementing
https://issues.jenkins-ci.org/browse/JENKINS-48792 this would be very
welcome. Until there is an implementation of JENKINS-48792 we cannot kill
off https://issues.jenkins-ci.org/browse/JENKINS-47859 and I am not sure
when I will next get a window to code stuff up...

But anyway!

Enjoy (once the release is synced)

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy0D3oJpqVuABKh33fjSw9oX9ADWDqunaGzjWV7xCjAGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Renaming credentials classes

[Carlos Sanchez]

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
> 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
> https://github.com/jenkinsci/credentials-plugin/blob/
> master/src/main/java/com/cloudbees/plugins/credentials/
> UserCredentialsProvider.java#L463
>
> The default store implementation delegates to the store's context
> https://github.com/jenkinsci/credentials-plugin/blob/
> master/src/main/java/com/cloudbees/plugins/credentials/
> CredentialsStore.java#L573
>
> So you seem to be using the correct XStream instances.
>
> /B
>
> 2017-12-29 13:01 GMT+01:00 Carlos Sanchez :
>
>> Hi
>>
>> Trying to get this PR to work on upgrades
>> https://github.com/jenkinsci/kubernetes-plugin/pull/268/file
>> s#diff-14316beac1f1489a56a52e21cf8e0ee6R506
>>
>> but none of the XSTREAM2.addCompatibilityAlias options listed in
>> https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining
>> +backward+compatibility seem to work, the credentials are never
>> deserialized
>>
>> Any suggestions?
>>
>> --
>> 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, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/CALHFn6Mo4zFSfMTi%2Bt%2BQQssS4%2B3Zd6Bstk3
>> qtbvcBAQoq-7OOA%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> *Robert Sandell*
> Software Engineer
> CloudBees, Inc.
> [image: CloudBees-Logo.png] 
> E: rsand...@cloudbees.com
> Twitter: robert_sandell
>
> --
> 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, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CALzHZS3PP_v7Q9sZC1JPZOR%2B2N%
> 3D-jet293vD6ACb_rh0ob6ZFA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OXppQWfNEN8ABAZRUUhb85KX08EVeJM2b%3DBiwf6H_b3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Renaming credentials classes

[Robert Sandell]

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
https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/UserCredentialsProvider.java#L463

The default store implementation delegates to the store's context
https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/CredentialsStore.java#L573

So you seem to be using the correct XStream instances.

/B

2017-12-29 13:01 GMT+01:00 Carlos Sanchez :

> Hi
>
> Trying to get this PR to work on upgrades
> https://github.com/jenkinsci/kubernetes-plugin/pull/268/files#diff-
> 14316beac1f1489a56a52e21cf8e0ee6R506
>
> but none of the XSTREAM2.addCompatibilityAlias options listed in
> https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+
> compatibility seem to work, the credentials are never deserialized
>
> Any suggestions?
>
> --
> 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, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CALHFn6Mo4zFSfMTi%2Bt%2BQQssS4%
> 2B3Zd6Bstk3qtbvcBAQoq-7OOA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] 
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS3PP_v7Q9sZC1JPZOR%2B2N%3D-jet293vD6ACb_rh0ob6ZFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

[lucamilanesio]

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 declarative 
> pipeline compatibility :-) 
>
> Luca. 
>
> > On 3 Jan 2018, at 18:16, Jesse Glick  wrote: 
> > 
> > On Wed, Jan 3, 2018 at 10:22 AM, Luca Milanesio 
> >  wrote: 
> >> If you want to submit feedback to Gerrit in your pipeline, just add the 
> following statement in your pipeline script: 
> >> 
> >> gerrit.review("Verified", 1, "It works !") 
> > 
> > I would urge you to use a plain old `Step` (no `workflow-cps` 
> > dependency except in `test` scope, no `GerritDSL` + `Gerrit.groovy`), 
> > e.g.: 
> > 
> > gerritReview status: 'Verified', vote: 1, message: 'It works!' 
> > 
> > You get a simpler implementation, *Pipeline Syntax* support, 
> > compatibility with Declarative Pipeline, and the chance to work 
> > unmodified with possible future execution engines. 
> > 
> > -- 
> > 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, send 
> an email to jenkinsci-dev+unsubscr...@googlegroups.com. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3DWgR4sZktwYLB_wuynLL8TURTMF-6F_f2wkUhTBoXBA%40mail.gmail.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a64a7487-d79a-4c25-aeff-e96645c4cfef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2.89.3 LTS RC testing started

[Oliver Gondža]

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 test plan 
https://wiki.jenkins-ci.org/display/JENKINS/LTS+2.89.x+RC+Testing


Thanks
--
oliver

--
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, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3b6fecba-63e5-abfe-1225-4969e0ffc55d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.