You could try and implement a BuildChooser:
https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/util/BuildChooser.java
Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications
From:
I just discovered a new packaging type in our repositories: jenkins-module
Can anyone elaborate on that type? what is is all about and how to use it?
an example of it is here: https://github.com/jenkinsci/domain-discovery-module/
...sorry if I missed a post about it...
Domi
--
You received this
Hi,
I created a pull request
https://github.com/jenkinsci/managed-scripts-plugin/pull/4.
But there were no reactions for more then a month.
So as suggested here
https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories I
now ask for the commit privileges.
My github user ist
Done. Welcome aboard!
Ulli
Am 30.06.2014 um 10:27 schrieb Dominik Ruf dominik...@gmail.com:
Hi,
I created a pull request
https://github.com/jenkinsci/managed-scripts-plugin/pull/4.
But there were no reactions for more then a month.
So as suggested here
Hi Oleg,
On 27 Jun 2014, at 17:11, Oleg Nenashev o.v.nenas...@gmail.com wrote:
I would need to learn about configuration migration, if you know of another
tool or example that performs this task please let me know.
please do not put `-plugin` in the artifactId.
The pattern is:
github repo name is: X-plugin
artifactId is: X
groupId is: org.jenkins-ci.plugins
package name is one of:
* org.jenkinsci.plugins.X; or
* jenkins.plugins.X; or
* com.mycompany.jenkins.X (if you want to credit a company providing
Hi Gurus!
I develop a new plugin for Jenkins and have to add some additional
properties to nodes. To do it, I extended class NodeProperty, so my
changes now are persisted by Jenkins. But now I want to replace Icon
displayed at /computer page for the nodes which I modified (in other words
for
https://issues.jenkins-ci.org/browse/JENKINS-21977 documents that the
HsErrPidList file is intentionally memory mapped so that hs_err_pid files
can be found easily.
Unfortunately, that means there are spurious failures when running
integration tests on windows (like many of the tests in
Nope, not in an easy way anyways. The icon names are “hard-coded” depending on
the state of the slave. You could do some ugly JS hack in you property’s
summary.jelly where you change the src value of the img tag. But that could
break as soon as core changes something on the page.
Robert
In summary: Allow broken build claiming post-build-action adds an Action
to any unsuccessful build. That Action is displayed on the results page
where users can click to claim or blame ownership of a build break. This
will occur at a random time after the build completes (i.e. long after
I think this would be somewhat difficult to implement, unless someone can
point to an extension point that could make it easier.
On Mon, Jun 30, 2014 at 10:19 AM, Marc Carter drekb...@gmail.com wrote:
In summary: Allow broken build claiming post-build-action adds an Action
to any unsuccessful
Hi,
As the latest governance meeting did not happen, Jesse and I have picked
new release line without much feedback. Letting you know that unless there
are serious objections 1.565 is going to be the next LTS.
This decision will be cast in stone when backporting starts on Wednesday.
--
Hmm, tough call. IIUC, multiple other plugins depend on
github-oauth-plugin, so it's bit painful to require such a cutting edge
version. But it's tolerable.
I wonder if it's possible to do that as an optional feature --- that if you
run on =1.569 you get that functionality, but it still degrades
So no workflow support in an lts release for a while then :-(
Big shame..
--
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
It's bit hackish, but if you copy SecurityListener class definition
verbatim into github-oauth-plugin in the jenkins.security package and put
@Extension(optional=true) to your implementation, then it'd work. When
running in =1.569 SecurityListener from the core will hide your private
copy, so
Oops the pr is
https://github.com/jenkinsci/github-oauth-plugin/pull/26
On Monday, June 30, 2014 2:27:59 PM UTC-5, Kohsuke Kawaguchi wrote:
Hmm, tough call. IIUC, multiple other plugins depend on
github-oauth-plugin, so it's bit painful to require such a cutting edge
version. But it's
teilo,
What does workflow support mean? Is it a new jenkins feature?
On Monday, June 30, 2014 12:59:55 PM UTC-5, ogondza wrote:
Hi,
As the latest governance meeting did not happen, Jesse and I have picked
new release line without much feedback. Letting you know that unless there
On 30.06.2014, at 23:26, Surya Gaddipati suryapraka...@gmail.com wrote:
What does workflow support mean? Is it a new jenkins feature?
https://github.com/jenkinsci/workflow-plugin (It doesn't even have a wiki page
yet!)
A plugin at version 0.1-beta-1, so far only released to the experimental
So... the whole idea of the shim plugin got me thinking a bit i.e. was
there an alternative that might be a bit easier to manage. I was wondering
why not just put the icon tag in a simple taglib of it's own (Vs putting
it in Jenkins Core + requiring the shim etc).
I quickly ran the idea by
You can't update core to use the plugin, as circular dependency... So as
soon as you want to use your tag in core your plugin is... Oh look its a
shim!
Would a rose by any other name smell as sweet?
On Monday, 30 June 2014, Tom Fennelly tom.fenne...@gmail.com wrote:
Hi.
We're in the process
Anyway you have over complicated yourself.
Also you don't call the shim tag icon-shim you call it icon but in a
different namespace. That makes migration simples
We should chat tomorrow
On Tuesday, 1 July 2014, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
You can't update core to
Hi all
I've submitted a small patch for the Promoted Builds Plugin that makes it
useful when also using the Version Number Plugin. It has a unit test update
and has passed the automated pull-request build.
https://github.com/jenkinsci/promoted-builds-plugin/pull/42
Would someone like to
Hi,
I have a new Gitlab Jenkins plugin currently on GitHub
here: https://github.com/DABSquared/gitlab-jenkins-plugin. My GitHub id is
bassrock and would like to host it on Jenkins.
Thanks!
Daniel
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers
23 matches
Mail list logo
