Hello Muhammad,
Thank you for your interest in the Code coverage api plugin! We have
office hours all this week, so we could discuss more about the project
during this time. See: https://jenkins.io/projects/gsoc/#office-hours for
office hour times.
(CCing Jenkins dev mailing list.)
On Tue, Feb
Since TFS supports git as a valid protocol, it might work with a git
repository hosted in TFS. Have you tried using TFS as a git server with
Blue Ocean?
It won't work with TFS using the TFS protocols.
Mark Waite
On Tue, Feb 20, 2018 at 2:21 PM Alex Yampolsky wrote:
> Our
Our organization uses Microsoft TFS as the standard for source control, is
there a way to integrate Blue Ocean pipeline creation with TFS ?
Appreciate the response !
Alex
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe
On Tue, Feb 20, 2018 at 8:41 AM, Baptiste Mathus wrote:
> For instance, I still cannot request myself a review on
> https://github.com/jenkinsci/configuration-as-code-plugin/pull/43
I think only someone with write permission to the repository can
request you. Without Daniel’s
Hi,
Thanks again for the interest. Just to provide some context to this thread,
Udara has reached out to me and Martin 2 weeks ago. Since EDA tools are not
the area of interest for the most of Jenkins devs, we decided to keep this
thread in private for a while until we have a rough scope
On Tue, Feb 20, 2018 at 8:00 AM, Antonio Muñiz wrote:
> Still, users could install the new plugin directly and get in troubles. I
> guess this can be solved by documentation and release notes in both plugins.
Or: https://issues.jenkins-ci.org/browse/JENKINS-49651
--
You
Declarative's when block, IIUC.
(Note: more a thread for the users list if we don't head over implementing
something in a plugin or so).
2018-02-20 12:00 GMT+01:00 Nigel Magnay :
> I have a project with a Jenkinsfile that changes a number of stages
> depending on whether
For some reason, it does not work, and wasn't before either for me. Not
everywhere at least, and not being admin, I couldn't check/understand why.
For instance, I still cannot request myself a review on https://github.com/
jenkinsci/configuration-as-code-plugin/pull/43
Maybe it's just because
> But note that existing users will not receive updates, and cannot
automatically "upgrade" to the new plugin
Making a tombstone release makes more difficult to get both plugins
installed.
1. Release the new plugin
2. Remove all the code from the old plugin
3. Leave a minimal pom.xml, with a
> On 20. Feb 2018, at 12:30, Petr Chudanič wrote:
>
> I have a Jenkins plugin that is hosted in Jenkins Update Centre.
>
> As we are considering to release new plugin with different name that would
> contain current plugin's functionality plus more we would like to remove
Hi Everyone
I have a Jenkins plugin that is hosted in Jenkins Update Centre.
As we are considering to release new plugin with different name that would
contain current plugin's functionality plus more we would like to remove it
from Update Center.
I'd like to know what is the correct
11 matches
Mail list logo