Re: Discussion: New Custom Jenkins WAR packaging tool

[Oleg Nenashev]

>
> We could introduce a new system property or environment variable pointing 
> to a custom WAR file 
> path for `WarExploder` to use, perhaps. 
>

Yes, I had something like that in my TODO list for the final impl.
It would require plugins to update to the recent JTH, but it's not a 
problem since we can always pass Maven property when running builds in 
CI/PCT. It may fail in some cases (upper bounds, new injected tests, etc.), 
but should work for the most of the plugins

Yes it does, but that has no direct effect on the file which is loaded by 
> `WarExploder`. The actual test runs will go back to the local Maven 
> repository for a `jenkins-war` artifact with the specified version number


It is fine with me, because Custom War Packager installs artifacts to the 
local repo anyway.
Obviously there are some limitations on groupId and artifactId to make such 
approach running, but it works.

BR, Oleg

On Thursday, March 22, 2018 at 9:00:12 PM UTC+1, Jesse Glick wrote:
>
> On Thu, Mar 22, 2018 at 2:58 PM, Oleg Nenashev  > wrote: 
> >> How would that work with JTH tests as run via PCT, since these will 
> only 
> >> pick up a Jenkins WAR from the local Maven repository 
> > 
> > JTH can take WAR from different sources, not only from local Maven 
> > repository (see WAR Exploder). I was a bit lazy during prototyping, so I 
> was 
> > just putting WAR to war/target/jenkins 
>
> Uh…but that is only supposed to be used from `jenkinsci/jenkins`. We 
> should not abuse that for other purposes. We could introduce a new 
> system property or environment variable pointing to a custom WAR file 
> path for `WarExploder` to use, perhaps. 
>
> > PCT supports "-war" option, which allows specifying a custom WAR path. 
>
> Yes it does, but that has no direct effect on the file which is loaded 
> by `WarExploder`. 
>
>
> https://github.com/jenkinsci/plugin-compat-tester/blob/4898b916f81f813d202721e1fe0eb36d222977a5/plugins-compat-tester/src/main/java/org/jenkins/tools/test/PluginCompatTester.java#L155-L207
>  
>
> It is only used to pick up metadata about the core version to test 
> against, the list of plugins and their versions to test, and some 
> miscellaneous stuff like that. The actual test runs will go back to 
> the local Maven repository for a `jenkins-war` artifact with the 
> specified version number, unless `WarExploder` is patched as discussed 
> above. 
>
> > Next week I will create a demo which actually runs JTH and PCT with a 
> custom WAR file within the repository. 
>
> Yes please—somehow verifying that the tests run against the actual 
> core and plugin versions specified in the YAML definition, even if 
> those are unreleased, present only in local source checkouts, etc.; 
> and that all plugins listed in the YAML are loaded during the test 
> execution, even if they are not present as `test`-scoped dependencies 
> in the POM of the plugin defining the test. 
>
> Also would be useful to see a demo of ATH tests running against this 
> WAR, with the same version constraints, and analogously verifying that 
> all listed plugins are loaded even if they are not mentioned in a 
> `@WithPlugins` annotation. 
>

-- 
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/d3c7ab12-626d-4654-9ff3-e50aaab66417%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

JEP: Modification of "Accepted" JEPs

[Liam Newman]

We recently had a pull request with a number of significant changes filed
against JEP-201 which has already been "Accepted" (see the JEP workflow
outlined in JEP-1 ).

https://github.com/jenkinsci/jep/pull/59

This poses a problem because the JEP workflow doesn't contain guidance for
making/tracking significant changes to JEPs.  The intent of the process is
for all major changes to land while the JEP is a "Draft". A JEP being
"Accepted" means that a general consensus was reached regarding the design
and scope of the component/area described by the JEP.  Once a JEP is marked
"Final", the workflow specifically states that changes should be made by
filing a new JEP and marking the old one as  "Superseded" when the new JEP
is complete.

I would like to add the following clarifications to JEP-1:

   1.  State specifically that all "significant changes" to a JEP should be
   completed before it is Accepted. This is pointed to in a number of places
   but may not be mentioned explicitly.
   2. Define a "significant change" is any change that would modify the
   intent, scope, API, or overall behavior of the component.  I will provide
   some examples.
   3. If "significant changes" are proposed to an "Accepted" JEP, it is be
   the responsibility of the Sponsor to communicate those changes on the
   mailing list and make sure that people have sufficient opportunity to
   review and comment before merging those changes.  A link to the thread
   should be included in the PR for the change and in the References section.
   4. If there are strong objections to the proposed change, the Reviewer
   of the JEP may choose to return the JEP to a "Draft" state for continued
   discussion and re-review.

(Items 1 and 2 are both clarifications. Item 3 is a reiteration of the
existing responsibilities of the JEP Sponsor in light of 1 and 2.  4 is a
reiteration of the existing of responsibilities and powers of the JEP
Review in light of 1 and 2.)

In the case of the above PR. it means that Ewelina would need to start a
thread on the mailing list to discuss this change and give people time to
review before we merge that change.

What do people think of this?  An feedback or suggestions?

Thanks,
Liam Newman
JEP-1 Sponsor

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

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[Oleg Nenashev]

The proposal looks good to me though it overlaps with "teams" a bit.

In GSoC we already use the channels and have regular meetings there. 
Regarding Youtube, it would be great to extend the number of participants 
beyond the current number (10) and to give "subject leaders" a permission 
to run HoA recordings for shareable sessions.

Gitter vs. IRC... I would vote for Gitter for 24/7 discussion rooms. 
#jenkins-meeting could be used for formal meetings tho.

BR, Oleg

On Thursday, March 22, 2018 at 10:31:04 PM UTC+1, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Thu, 22 Mar 2018, Jesse Glick wrote: 
>
> > On Thu, Mar 22, 2018 at 5:04 PM, R. Tyler Croy  > wrote: 
> > > Regularly scheduled and published meetings. I can easily imagine 
> re-using 
> > > #jenkins-meeting or our public YouTube channel for regularly 
> scheduling 
> > > and hosting weekly meetings for these various groups. 
> > 
> > gitter.im feels more accessible than IRC, and automatically archived. 
>
>
> Gitter is logged, but that's a far cry from the meeting notes which we're 
> able 
> to automatically generate and archive on http://meetings.jenkins-ci.org/ 
> :-/ 
>
> I haven't found a preponderance of good "gitter" bots out there on the 
> internets yet. 
>
>
> That said, in the context of the SIGs proposal, I don't have a strong 
> opinion 
> on where people have meetings, so long as they're published on a calendar 
> ahead 
> of time, are open, and are recorded in some form or fashion. 
>
>
> Cheers 
> - 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/c917e50e-e56b-4951-a333-a9c7f4045429%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: @QueryParameter in form validation is not filled for dropdownDescriptorSelector

[Ullrich Hafner]

Ok, thanks. I created an issue: JENKINS-50355. Maybe the problem is that the 
views are in different plugins and are loaded by different class loaders...

> Am 21.03.2018 um 23:27 schrieb Jesse Glick :
> 
> On Wed, Mar 21, 2018 at 3:53 PM, Ullrich Hafner
>  wrote:
>> Is there anything different with a dropdownDescriptorSelector?
> 
> No, it should work.
> 
> --
> 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/CANfRfr1MAavT6qERsd7MbgqertN91wxecedYiw0MUZm%2BdUAYyg%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/A0200A39-1F1D-40FF-A614-C965A8281631%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: form round trip tests fail after upgrading to jenkins version 1.642.3

[Martin Weber]

Am Dienstag, 20. März 2018, 21:00:31 CET schrieb Martin Weber:
> To implement pipeline compatibility for the cmakebuilder plugin[1], I
> changed the required jenkins version from 1.580.3 to 1.642.3.
> Parent pom version is 2.7.
> 
> With 1.643.3, my form-round-trip tests [2] fail with 'internal server
> error'. I also ran the test from eclipse, which gave me some more output in

I examined this a little further.
To be precise: Code base was unchanged, just the jenkins version changed.
I always ran 'mvn clean verify'.

For the records, here is what I did:

1.580.3 --> 1.642.3: BUILD FAILURE
1.642.3 --> 1.642.1: BUILD SUCCESS 
1.643.1 --> 1.642.2: BUILD SUCCESS
1.643.2 --> 1.642.3: BUILD SUCCESS (what?)

removed org.jenkins-ci directory from local maven cache --> BUILD SUCCESS???
removed org.jenkins-ci directory from cache; 1.580.3 --> BUILD SUCCESS (as 
expected)
1.580.3 --> 1.642.3: BUILD SUCCESS
removed org.jenkins-ci/main/core/1.580.3 directory from cache

Weird.

/Martin

-- 
E-Mails sollten Text sein, Text und nur Text.
Wenn Gott gewollt hätte, dass E-Mails in HTML geschrieben würden,
endeten Gebete traditionell mit .

-- 
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/7687954.YpIfe6VxWV%40linux.
For more options, visit https://groups.google.com/d/optout.

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[R. Tyler Croy]

(replies inline)

On Thu, 22 Mar 2018, Jesse Glick wrote:

> On Thu, Mar 22, 2018 at 5:04 PM, R. Tyler Croy  wrote:
> > Regularly scheduled and published meetings. I can easily imagine re-using
> > #jenkins-meeting or our public YouTube channel for regularly scheduling
> > and hosting weekly meetings for these various groups.
> 
> gitter.im feels more accessible than IRC, and automatically archived.


Gitter is logged, but that's a far cry from the meeting notes which we're able
to automatically generate and archive on http://meetings.jenkins-ci.org/ :-/

I haven't found a preponderance of good "gitter" bots out there on the
internets yet.


That said, in the context of the SIGs proposal, I don't have a strong opinion
on where people have meetings, so long as they're published on a calendar ahead
of time, are open, and are recorded in some form or fashion.


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


signature.asc
Description: PGP signature

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[Jesse Glick]

On Thu, Mar 22, 2018 at 5:04 PM, R. Tyler Croy  wrote:
> Regularly scheduled and published meetings. I can easily imagine re-using
> #jenkins-meeting or our public YouTube channel for regularly scheduling
> and hosting weekly meetings for these various groups.

gitter.im feels more accessible than IRC, and automatically archived.

-- 
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/CANfRfr1EYwT6vj-pKESYXe_5%3D9K6nz-X7QTiM5Eg62WaEUBoLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[R. Tyler Croy]

I have been looking at some of the great things the Kubernetes community has
been doing for ideas we can borrow, and one idea which really sticks out is:
Special Interest Groups (SIGs)


A full list of the Kubernetes community SIGs can be found here:


I think we already have some groups, which are almost informal SIGs, such as
Security, GSoC, Infra, etc. The aspects of SIGs which I really would like to
formalize, and support from a community infra standpoint are:

* Clear problem domain/focus area.
* Regularly scheduled and published meetings. I can easily imagine re-using
  #jenkins-meeting or our public YouTube channel for regularly scheduling
  and hosting weekly meetings for these various groups. I run a weekly
  infra team sync on jenkins.io/hangout for example, but that's not
  recorded anywhere :(
* "Chairs" (i.e. team leads)
* Dedicated discussion channel/group (i.e. mailing list)


Some SIGs which I would love to see for starters, would be:

 * Security, lead by Daniel
 * GSoC, lead by Oleg
 * Infra, lead by Olivier and myself
 * Cloud Native (Kubernetes, Jenkins X, CLOUD, etc), lead by Carlos
 * Essentials, lead by myself
 * LTS, lead by Oliver
 * Automation/Configuration (config as code, puppet, chef, etc), lead by Ewelina


>From my part on the infrastructure side, I'm more than willing to do the
necessary work to support SIGs, as I really feel like they will help bring more
folks to the table for focused contribution to the Jenkins project.


I'm curious how others feel about a SIG structure and whether you all agree
that it will help channel/focus discussions and contributions?



If there's strong interest, I'm happy to take point on writing a Process JEP.


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


signature.asc
Description: PGP signature

Re: Discussion: New Custom Jenkins WAR packaging tool

[Jesse Glick]

On Thu, Mar 22, 2018 at 8:25 AM, Oleg Nenashev  wrote:
> It allows the custom configuration to be transparently
> used with existing tests.

How would that work with JTH tests as run via PCT, since these will
only pick up a Jenkins WAR from the local Maven repository? Do you
need to `mvn install:install-file` the custom WAR as a `SNAPSHOT`
version that can be fed to PCT?

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

Re: java.nio.channels.ClosedByInterruptException when I click cancel button from a running job

[Jesse Glick]

On Wed, Mar 21, 2018 at 5:33 PM, Daniel Anechitoaie
 wrote:
> java.lang.InterruptedException
> at hudson.model.Build$BuildExecution.build(Build.java:214)

So this is from

https://github.com/jenkinsci/jenkins/blob/3b5c715ae0d00ec3a38c63d8c9bf9de2a76b9e29/core/src/main/java/hudson/model/Build.java#L212-L214

I suspect that code is wrong—see below.

> But in Jenkins build log it just stops and nothing is displayed.

Not sure what would cause that. The stack trace implies that the
`InterruptedException` should be caught here:

https://github.com/jenkinsci/jenkins/blob/3b5c715ae0d00ec3a38c63d8c9bf9de2a76b9e29/core/src/main/java/hudson/model/Run.java#L1740-L1745

as apparently happened in your `Thread.sleep` test builder. Perhaps
the ZIP function is not interruptible, which is too bad, but then the
symptom should merely be that the ZIP proceeds to completion, and then
the build is shown as aborted in the normal way.

> If I cancel during the HTTP upload part there I get the 
> java.nio.channels.ClosedByInterruptException

That would be consistent with my hypothesis that the thread interrupt
flag is not getting cleared. Check if this helps either or both of
your cases (ZIP and HTTP) without regressing the `sleep` case:

diff --git a/core/src/main/java/hudson/model/Build.java
b/core/src/main/java/hudson/model/Build.java
index 15aed23050..7f2fbbbc34 100644
--- a/core/src/main/java/hudson/model/Build.java
+++ b/core/src/main/java/hudson/model/Build.java
@@ -208,8 +208,7 @@ public abstract class Build ,B extends Build>
 return false;
 }

-Executor executor = getExecutor();
-if (executor != null && executor.isInterrupted()) {
+if (Thread.interrupted()) {
 // someone asked build interruption, let stop the
build before trying to run another build step
 throw new InterruptedException();
 }

-- 
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/CANfRfr2TYH6xmgCm%3DtOZ_D4n%2BqMtfmi7SLGNKNphoWL7KhJd0g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: POTD: Jenkinsfile Runner

[Jesse Glick]

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 invisible WorkflowRun, right?

Yes, that seems to be the safest approach.

> I was thinking you'd just put assert statements into Jenkinsfile and that 
> should already work. Granted, I haven't tried it so maybe it doesn't work.

Groovy “power-asserts” work in Pipeline script as far as I know.

-- 
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/CANfRfr3e92S1hvsAZBEMeh3%3DgWFSun%2Bc0SPYZb3irezbxywn3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Discussion: New Custom Jenkins WAR packaging tool

[Oleg Nenashev]

Hi all,

Currently I am working on setting up testing flows for my prototypes
(e.g. JENKINS-38313
- External Build Logging
 or JENKINS-44100 -
Detach Remoting logic from the core
). Such prototypes
include multiple components including unreleased core patches and plugins.
Our current test frameworks (Jenkins Test Harness, Acceptance Test Harness,
Plugin Compatibility Tester) are mostly focused on WAR file testing, so I
would need to package the prototypes as WAR files in order to run tests.

In order to achieve the goal, I have created a new packaging tool:
https://github.com/oleg-nenashev/jenkins-war-packager, which is generally a
maven-hpi-plugin:custom-war
 on
steroids. It can run as CLI tool and as a Maven plugin. The tool takes the
WAR as a YAML definition (example
)
and packages everything as a single WAR file:

   - Base WAR (including dev branches from Git/filesystem)
   - List of plugins and libraries to be bundled (including dev branches
   from Git/filesystem)
   - List of system properties to be pre-set
   - Groovy Hook Scripts
   to bundle
   (may also support Configuration-as-Code plugin
    later)

WAR file includes system properties and Groovy hooks, so it may configure
itself on startup. It allows the custom configuration to be transparently
used with existing tests.

I have created two examples for the tool:

   - External Task Logging for ElasticSearch
   
-
   A prototype we created together with Jesse Glick in 2016. It packages extra
   plugins and preconfigures them
   - Jenkins - all latest WAR
   

   - Automatic build of the Jenkins core with latest dependencies (Stapler,
   Remoting, modules)

In the current state I consider Custom Jenkins War Packager to b e a
development tool only. It can be potentially used to package Jenkins WARs
for production use, but IMHO it would require more work before it can be
advertised (standardized specification format, support of Docker packaging,
etc.). But Jenkins developers may find the tool useful even in the current
state. So I would like to get it hosted within Jenkins organization and
released as an alpha version.

If you are interested in such packaging and development tool for Jenkins, I
would appreciate any feedback.

Best regards,
Oleg Nenashev

-- 
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/CAPfivLBEF%3DQD4XzkxYOfQhPTKERrFnHhWwNaCgWB%2B69zHfixwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSOC - Office Hours 3-23-18

[Oleg Nenashev]

I'd bet it's what Steven meant.
Yesterday he joined the office hours call at 2 AM :)

Just to provide a full list of planned sessions, here is what we are 
planning now:

   - Mar 22, 06:00-07:00 PM UTC - EDA plugins project ideas sync-up
   - Mar 23, 08:00-09:00 AM UTC - General Q session
   - Mar 26, 08:00-09:00 AM UTC - General Q session
   - Mar 26, 06:00-07:00 PM UTC - General Q session

All sessions will be conducted in the Jenkins hangout 
 channel. I will send a separate announcement 
in few minutes.

BR, Oleg

On Wednesday, March 21, 2018 at 10:59:43 PM UTC+1, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Wed, 21 Mar 2018, Oleg Nenashev wrote: 
>
> > Hi Tyler, 
> > 
> > I will update the website in few hours. 
> > I also plan to setup other last-chance timeslots, so I will make changes 
> in 
> > a bulk mode. 
>
> I am also going to guess that Steve did not mean 8am UTC, which I believe 
> is 
> 11pm in his/our timezone :) 
>
>
>
> - 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/269b9029-07be-4765-9c9b-25fbf748d9c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.nio.channels.ClosedByInterruptException when I click cancel button from a running job

[Daniel Anechitoaie]

I’ve added two replies to this thread by my emails keep getting deleted and 
they don’t appear on the group on the web.
Have i did something wrong?



> On 21 Mar 2018, at 17:32, Jesse Glick  wrote:
> 
> On Wed, Mar 21, 2018 at 7:12 AM, Daniel Anechitoaie
>  wrote:
>> [Is it] possible maybe one of these libraries? […]
>> 
>> I tried a test with just a bunch of Thread.sleep() before it gets to my code
>> (that zips the files and HTTP puts them) and if I cancel the job there it
>> gets aborted nicely and is handled properly by Jenkins.
> 
> So sounds like a problem in the interaction between the behavior of
> those libraries and Jenkins interrupt handling. Again I suspect that
> something is catching interrupts, proceeding without throwing
> `InterruptedException`, but then setting the thread interrupt flag and
> this gets ignored up until the moment the build record is being
> finalized and the NIO calls made from `AtomicFileWriter` check the
> flag. If true, the solution would probably be for the code which runs
> an individual build step (somewhere in `AbstractBuild` IIRC) to check
> the interrupt flag and throw `InterruptedException` at that time.
> Could be verified in a `JenkinsRule`-based test by having a
> `TestBuilder` which mimics the relevant behavior of these libraries.
> 
> I doubt this particular issue could apply to Pipeline builds, though
> there might be other ways in which interrupt handling is incorrect
> there as well.
> 
> -- 
> 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/BSL0N5UwyC8/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/CANfRfr1G3%3DVt28Y2pXupBTUVdsw-D%3DOBpkqv-%3Dw4sTtdoxsOyg%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/25DD2FFF-B0F2-40AA-9E22-A4D418CEDEA3%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC 2018] [Student Introduction] Cloud Features for External Work-space Manager Plugin

[Vineeth Reddy]

I am familiar with java ,maven and Microsoft azure as this project needs
some cloud experience.
But I am unable to get on to the implementation part.
I am new to open source community
May be am not good enough for the project.
As implementation part is still a challenge to me am unable to come up with
timeline part in application.




On Wed, 21 Mar 2018 at 4:39 AM, Oleg Nenashev 
wrote:

> Hi Vineeth,
>
> Generally you tell us. In GSoC mentors propose "project ideas", but
> students have a freedom to adjust these ideas to their vision and
> interests. Since you have gone through the linked materials and issues,
> what is your impression? Which topics would you prefer to work on? Please
> do not hesitate to ask in JIRA tickets or in this thread if something is
> not clear.
>
> Best regards,
> Oleg Nenashev
>
>
> On Tuesday, March 20, 2018 at 8:04:52 PM UTC+1, Vineeth Reddy wrote:
>
>> I went through all the resources provided and would like to know more
>> about cloud features required for this project.
>>
>> On Sun, 18 Mar 2018 at 3:21 AM, martinda  wrote:
>>
> Hi,
>>>
>>> I should also mention that there are videos that explain how the
>>> external workspace manager plugin works.
>>> These provide good starting points for understanding from the user point
>>> of view.
>>>
>>> 1. Lightning talk (Jenkins World 2016):
>>> https://www.youtube.com/watch?v=mZaCngHQaO4
>>> 2. GSoC 2016 final presentations (first presentation is the external
>>> workspace manager plugin): https://youtu.be/lo8sZJt2WhM?t=404
>>>
>>> Martin
>>>
>>>
>>> On Friday, March 16, 2018 at 10:16:10 PM UTC-4, martinda wrote:

 I forgot to mention that we have office hours and all students are
 invited to participate and ask questions about GSoC.
 See https://jenkins.io/projects/gsoc/#office-hours for the times.

 Martin

 On Friday, March 16, 2018 at 9:50:28 PM UTC-4, martinda wrote:
>
> Hello Vineeth,
>
> Thank you for your interest.
>
> We have some student information, but it looks like you have already
> read it: https://jenkins.io/projects/gsoc/students/
> If you find something is missing please let us know.
>
> If you have already studied the external workspace manager code base
> and know the extension points
> ,
> then I recommend familiarizing yourself with cloud based storage, for
> example azure, amazon, google, etc. This should help you write your 
> project
> proposal.
>
> Best Regards,
> Martin d'Anjou
>
> On Friday, March 16, 2018 at 3:18:03 PM UTC-4, Vineeth Reddy wrote:
>>
>>
>> I am a newbie in open source community but i feel i am capable enough
>> to understand and give back to community my best.
>>
>> I am interested in working with "CLOUD FEATURES FOR EXTERNAL
>> WORKSPACE MANAGER PLUGIN. "
>>
>> I spent decent time on understanding project and would like to look
>> into it more detail.
>>
>> As application closes in 11 days. I am unable to contribute much in
>> prior but would like to make it this summer.
>>
>> Please guide with through additional info, resources on this project
>> and ways to selected for this project and in starting  the contribution
>> right away.
>>
>> --
>>> 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/6BgDrjm6_Lk/unsubscribe.
>>>
>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-de...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/34c19ab7-b00f-4336-9d11-661b761f5cb4%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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/6BgDrjm6_Lk/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/3c6e0de6-c1a7-48e2-86c4-8ba1599852d3%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