Re: Windows builds/tests for core disabled

[Daniel Beck]

> On 06.02.2017, at 18:23, Slide  wrote:
> 
> Just skipping them seems too hacky to me.

IMO we should get Windows testing back ASAP -- so if skip on Windows + TODO 
comment gets us there more quickly, we should do so.

While it doesn't improve the Windows coverage, it will at least prevent 
regressions.

-- 
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/44B2E1D6-B1D7-4938-BCE3-0983EDEE4909%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Is there any docker plugin which does not save credentials in the slave machine for docker image push

[AYUSH SAHU]

Hi,

I don't want to save credentials inside docker.cfg or .docker/config.json in 
the 
jenkins slave for docker push.

Is there any docker plugin which does not save credentials in the slave machine 
for docker image push.


Regards,

Ayush


-- 
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/e4fcef4b-b98d-49e7-9dab-195a6a489499%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: lockable resource plugin needs some love

[Staffan Forsell]

OK, thanks. Both of these are really must fix issues for a lock plugin. I 
will watch status changes to these issues and could test any pre-release 
(of JENKINS-40879) if necessary.
/Thanks

On Monday, 6 February 2017 16:31:15 UTC+1, Jesse Glick wrote:
>
> On Mon, Feb 6, 2017 at 5:10 AM, Staffan Forsell  > wrote: 
> > there is currently some serious bugs in the lockable resources latest 
> > release 1.11. 
>
> JENKINS-40368 is already on the roadmap for someone from CloudBees to 
> work on; I can add a note about JENKINS-40879. I cannot promise a 
> timeline. 
>

-- 
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/1723e7db-8772-41c7-89eb-ca1670d7c305%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Windows builds/tests for core disabled

[Slide]

(replies inline)

On Mon, Feb 6, 2017 at 10:11 AM R. Tyler Croy  wrote:

> (replies inline)
>
> On Sun, 05 Feb 2017, Slide wrote:
>
> > I won't be at the hackathon, but I'll take a look. Some of the tests were
> > written without any windows considerations taken into account, so the
> > sooner we can get this fixed (so people who write new tests get feedback
> on
> > windows being broken by them) the better.
>
> Is there a compelling reason not to just mark all these failing tests as
> skipped on the Windows platform and move on?
>

Well, from what I can see, several of the tests are just newline issues,
people expect \n only, when on Windows it should be \r\n. I don't think we
should skip tests for just that reason, we should fix as many of the tests
as possible so that we have as good of coverage on Windows as on Linux.
Just skipping them seems too hacky to me.



>
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>  xmpp: rty...@jabber.org
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/20170206171055.GU26439%40blackberry.coupleofllamas.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/CAPiUgVfmJ0CzKKQ09Su%3D1dYQirW8xvzMq1rP-v%2BCY2vBPa0d7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Windows builds/tests for core disabled

[R. Tyler Croy]

(replies inline)

On Sun, 05 Feb 2017, Slide wrote:

> I won't be at the hackathon, but I'll take a look. Some of the tests were
> written without any windows considerations taken into account, so the
> sooner we can get this fixed (so people who write new tests get feedback on
> windows being broken by them) the better.

Is there a compelling reason not to just mark all these failing tests as
skipped on the Windows platform and move on?



- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
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/20170206171055.GU26439%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: lockable resource plugin needs some love

[Jesse Glick]

On Mon, Feb 6, 2017 at 5:10 AM, Staffan Forsell  wrote:
> there is currently some serious bugs in the lockable resources latest
> release 1.11.

JENKINS-40368 is already on the roadmap for someone from CloudBees to
work on; I can add a note about JENKINS-40879. I cannot promise a
timeline.

-- 
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%3DhU7-pFRuZtz8oSMpsORDWUVGckNp9wQBdFGdN-zX0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Groovy Postbuild] Place link to other view/job in build summary

[Marcin Zajączkowski]

Hi,

I would like to make a reference to an other view or job (optionally also a 
run) from a build/run summary page using Groovy postbuild. I know I can 
take an URL for a view (with getAbsoluteUrl()) and put it directly as a 
link, but it 's quite ugly and has side effects. I wonder if there is a 
better way.

What is a recommenced way to put a link to a view or a job (having a 
reference to a View or Job already) on a build summary page?

Marcin

-- 
http://blog.solidsoft.info - Solid Soft - Working code is not enough

-- 
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/65816cfe-c921-4005-a185-4300952866e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: It looks like a server is down that is breaking all the plugin pages

[Moshe Cohen]

I guess the server got rebooted by the time you saw this :-)

The Jira plugin page was just an example, it was true for all plugin pages.
The top section "Plugin information" was showing a timeout error.
All OK now.

On Mon, Feb 6, 2017 at 11:10 AM, Oleg Nenashev 
wrote:

> Well, I see no issues there excepting the broken JIRA queries.
> Please also write such notifications to the INFRA team mailing list to get
> a quick response
>
> понедельник, 6 февраля 2017 г., 2:17:23 UTC+1 пользователь Moshe Cohen
> написал:
>>
>> e.g. see top of https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/HtEVGk2sCCc/unsubscribe.
> To unsubscribe from this group and all its topics, 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/a8c16f0b-83cc-4787-af69-b2b264b6e266%
> 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/CAL%3Dvx5vzOtz2aAuu%2BAwJLBx8%2BfDiykTtgM7kw9XVeKn1G7DrNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

lockable resource plugin needs some love

[Staffan Forsell]

Hi, there is currently some serious bugs in the lockable resources latest 
release 1.11. This is also the only version of plugin supporting locking to 
labels using the pipeline.
Especially the bug https://issues.jenkins-ci.org/browse/JENKINS-40879 for 
is pretty critical since it basically makes locks in pipeline useless.
There has also been a little lack of response now for a while and I was 
hoping that someone would like to make an effort to fix it since there it's 
pretty reproducible using the comments the issue .

/Thanks Staffan

-- 
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/2cead11c-2802-449c-81f0-0f422ac06d06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: It looks like a server is down that is breaking all the plugin pages

[Oleg Nenashev]

Well, I see no issues there excepting the broken JIRA queries.
Please also write such notifications to the INFRA team mailing list to get 
a quick response

понедельник, 6 февраля 2017 г., 2:17:23 UTC+1 пользователь Moshe Cohen 
написал:
>
> e.g. see top of https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin
>

-- 
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/a8c16f0b-83cc-4787-af69-b2b264b6e266%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly/Plugin pipeline script support for optionalBlock

[Andrew Sumner]

Is there any other options for creating foldable sectionsthat will also work 
with the pipeline syntax generator? optionalBlock: will not add the fields 
inside the foldableblock to the generated syntaxoptionalProperty: couldn’t get 
that to work and I’m notsure that it will indent the child fields like 
optionalBlockSimple independent fields: lose visual queue that field 
isdependant on another field being set 

On Thursday, 19 January 2017 5:13 AM, Jesse Glick  
wrote:
 

 On Tue, Jan 17, 2017 at 7:55 PM,   wrote:
> When updating a plugin to support pipeline script, how do I handle an
> optionalBlock section?

Do not use `f:optionalBlock`. This is a low-level control. Do not
refer to `JSONObject` either. All this is old-style deprecated form
binding.

Use a high-level control like `f:optionalProperty` for nullable
structs (`ui-samples-plugin` has an example), or simple independent
`f:checkbox`es for `boolean` properties (`doCheck*` form validation
can reject invalid combinations).

Also use `@DataBoundSetter` for any property with a plausible default.

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-dev/uGVIkV7u78Y/unsubscribe.
To unsubscribe from this group and all its topics, 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/CANfRfr0KKVKGvJzvgBBAEGdDNshQ%3DY8wgtrzyXsuPst4y60fag%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/673807624.2364733.1486370659547%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.