Parsing report files produced by static code analysis is something that is
valuable also outside Jenkins community. That is why I think it should be
implemented in a library and released to Maven Central, not only Jenkins
Maven repos. And so I have done (
Hey guys,
Thank you so much for the response. I am sorry for the late reply because
of school and I would like to find a good time to write this email. I will
be integrating Jenkins with my project and share a Google Docs with you
guys about my thoughts and what features I think can be useful
On Thu, Mar 10, 2016 at 8:24 PM, Andrew Bayer wrote:
> Advice?
Do not touch any of this, and write your functionality as a Groovy
library, using low-level `Step`s as needed for logical processing.
`ParallelStep` is very special—that is why it is implemented in the
same
So
https://github.com/jenkinsci/workflow-plugin/blob/30a80b44ef524333165ed59b25de30daf1b2a99d/cps/src/main/java/org/jenkinsci/plugins/workflow/cps/DSL.java#L116
- right now, the parallel step is the only step that can act as a container
for further steps without having those further steps directly
Yes, I believe "jobs" contains the number of each job type present.
"version" should be the Jenkins version, e.g. "1.567.8"
On 10/03/16 16:31, Payal Priyadarshini wrote:
Hey Kohsuke & Daniel,
I fetched the fields of census data using mongodb and tried to document
it for the future use.
Did you try to get in contact with the current maintainer? Seems like Simon did
a couple of releases in 2015.
> Am 10.03.2016 um 03:27 schrieb Lewis Vail :
>
> Hey,
>
> I submitted a pull request
> (https://github.com/jenkinsci/ci-game-plugin/pull/18
>
Hi Winstone. Yes if you had some concrete ideas on an area you think you
could contribute to - start and share a Google doc (we can flesh out the
idea on it). Otherwise there are office hours where ideas can be thrown
around.
On Wed, 9 Mar 2016 at 5:45 PM, Oleg Nenashev
There is already one api (which is used by gerrit) to contribute messages -
and there is an implementation that picks up findbugs/checkstyle from the
existing plugins.
It would be great if these could all be aligned so there was one message
contributing api - then all you need is a single
On 10.03.2016, at 20:43, James Nord wrote:
> Why include CVS when Perforce is not included?
I included P4 Plugin, rather than Perforce Plugin, based on a recommendation by
Oleg.
--
You received this message because you are subscribed to the Google Groups
"Jenkins
The XML file is created from scratch when you save/apply from the UI with
XStream so there is no easy way to do this.
On Wednesday, March 9, 2016 at 6:01:59 PM UTC, amaterasu48 wrote:
>
> I have developed a client application that lets me edit the Jenkins job
> config XML file and push the
we want to distinguish error due to job misconfiguration (bad docker image
ID for sample) and infrastructure issue (no available resources)
2016-03-10 19:58 GMT+01:00 Suckow, Thomas J :
>
>
> On 3/9/16, 12:40 PM, "jenkinsci-dev@googlegroups.com on behalf of Jesse
> Glick"
>
> Could also be interesting if you are shutting down Jenkins and don't wan't
> to wait for a build to complete
use pipeline and then your builds will then mostly survive Jenkins restarts.
Or there is a proprietary restart aborted builds
Firstly upgrade to Java8 to get rid of the PermGen :)
Secondly as this is permgen this sound like dynamic classes that are
created for groovy may not getting disposed correctly so have some
references somewhere - so I would use Java8 and get a heap dump and
investigate from there.
Something
Why include CVS when Perforce is not included? do we expect people who are
still using CVS to suddenly think they need a CI system rather than a
change of SCM :-)
I would think that both are equally niche markets these days (for very
different reasons) - so include both or neither.
On
On Thursday, March 10, 2016 at 10:58:38 AM UTC-5, Daniel Beck wrote:
>
>
> On 10.03.2016, at 16:17, Samuel Van Oort > wrote:
> >
> > Embeddable build status plugin would be a strong candidate for
> inclusion. I'm not sure what category would be best, but
It would be an interesting feature if a build could be returned to the queue. I
would actually like that in the case the slave disappeared during the build,
I've had that happen a couple times over the last few years. Could also be
interesting if you are shutting down jenkins and don't wan't to
On 3/9/16, 12:40 PM, "jenkinsci-dev@googlegroups.com on behalf of Jesse
Glick"
wrote:
>
>Or just fail the build and the next one should work.
I just don't want to have to kick builds when a normal slave would "just
wait". Our
As per https://issues.jenkins-ci.org/browse/JENKINS-33358 we experienced
some severe issues due to permgen memory leaks. This seems to be related to
use of Groovy, which is quite concerning given the use of it with Jenkins
(e.g. pipeiline plugin). This seems to be a serious issue but we have
On 10.03.2016, at 16:17, Samuel Van Oort wrote:
>
> Embeddable build status plugin would be a strong candidate for inclusion.
> I'm not sure what category would be best, but "Organization and
> Administration" and "Build Features" both make some sense.
Noted. FWIW I
On 10.03.2016, at 16:39, Robert Sandell wrote:
> What makes antisamy-markup-formatter an Organization type plugin? I would
> have thought it to be Security related?
The default is no formatting at all (escaping all the things). This allows you
to use a 'safe' subset
What makes antisamy-markup-formatter an Organization type plugin? I would
have thought it to be Security related?
/B
On Thu, Mar 10, 2016 at 4:17 PM, Samuel Van Oort
wrote:
> The list looks generally really solid (as do the recommendations).
>
> Looking at it, a couple
Hey Kohsuke & Daniel,
I fetched the fields of census data using mongodb and tried to document it
for the future use. Although, I have few questions about some of the
fields, which is marked in red.
Thanks.
Payal Priyadarshini
install-ID
is a list, where each element contains 7 fields.
The list looks generally really solid (as do the recommendations).
Looking at it, a couple comments:
- Would it make sense to put parameterized trigger in the initial
recommended plugins?
- Is gradle plugin use strong enough to make it part of the core
recommended plugins?
- Junit &
Thanks Daniel!
On Thu, Mar 10, 2016 at 3:40 PM, Daniel Beck wrote:
> Done!
>
> On 10.03.2016, at 10:32, Antonio Muñiz wrote:
>
> > There we go! :)
> >
> > On Thu, Mar 10, 2016 at 9:22 AM, Robin Jarry
> wrote:
> > Hi all,
> >
> >
Done!
On 10.03.2016, at 10:32, Antonio Muñiz wrote:
> There we go! :)
>
> On Thu, Mar 10, 2016 at 9:22 AM, Robin Jarry wrote:
> Hi all,
>
> Antonio has accepted to help on maintaining the plugin.
>
> Could it be possible to add him in the
AFAIK non-default `View`s should be in the ancestor list.
--
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
Hi !
Yoann and I, who applied as mentors on this topic, both live in Rennes, so
we could easily discuss this in mode details.
Our plan is to investigate how Jenkins could better rely on a Docker
infrastructure. We already have some proof-of-concept code, but now need to
inject into jenkins-core
Hi Tyler,
This is Mohan Krishna ,working as a QA Automation Engineer.
I was interested in Test Automation Project in GSoc-2016, Unfortunately i
couldn't participate.
As per Oleg reference, there has been some Ruby stuff when i can lend my
hand and help the team.
Looking forward for a reply from
Hello, everyone!! Sorry to present myself after the discussions. Because i
had the exam in the beginning of this week.
My name is Guobao. I'm the student of Polytech Nantes, and i am studying
Informatique(SILR: système informatique, logiciel et réseaux) in the 4th
year. I am following a
Hi,
is there a possibility to get the current view in a FormValidation?
I want to extend the view configuration (with ViewProperty). Therefore I
created some fields.
Now I need the current view in my FormValidation method. There's an
annotation @AncestorInPath, but this only works for items
please see
https://github.com/jenkinsci/one-shot-executor-plugin/commit/86c632091391e3204432a8c7d1a18bb48b3a66e3
basically, this on let the provisionner keep a task in the Queue when it
can determine it hasn't enough resources to run extra slaves.
this can be used to prevent overload, or allocate
There we go! :)
On Thu, Mar 10, 2016 at 9:22 AM, Robin Jarry wrote:
> Hi all,
>
> Antonio has accepted to help on maintaining the plugin.
>
> Could it be possible to add him in the "lockable-resources-plugin
> Developers" group on github?
>
> His github ID is @amuniz
>
>
Hi all,
Antonio has accepted to help on maintaining the plugin.
Could it be possible to add him in the "lockable-resources-plugin
Developers" group on github?
His github ID is @amuniz
Thanks in advance.
--
Robin
--
You received this message because you are subscribed to the Google Groups
33 matches
Mail list logo