Hello,
I'd be glad to pass the maintenance of this repo to somebody else, as I no
longer use Stash for any projects.
I stayed in case some housekeeping was needed but I don't plan any serious
work here.
Best,
Jakub Bocheński
On Mon, Aug 19, 2024 at 7:57 PM Roberto Moura
wrote:
&
Interesting idea, I can indeed add credentials to a user in
JENKINS_URL/user/USERNAME/credentials/store/user/domain/_/
I assume those credentials are only available to the user who uploaded them?
Jakub Bocheński
On Thu, Aug 20, 2020 at 6:51 PM 'Gavin Mogan' via Jenkins Developers &
entials parameter.
The whole point is to allow users to upload a certificate, so that won't
help.
Jakub Bocheński
On Wed, Aug 19, 2020 at 10:03 PM Jesse Glick wrote:
> On Mon, Aug 17, 2020 at 10:10 AM kuba.bo...@gmail.com
> wrote:
> > My problem with file parameter is that the
For now I just use this script to delete the file after build
// do not store the secret files on master's disk
systemGroovyCommand('''
import java.io.File;
new File(build.getRootDir(), "fileParameters").deleteDir();
''')
On Mon, Aug
Found https://issues.jenkins-ci.org/browse/INFRA-2319
On Friday, November 15, 2019 at 5:26:56 PM UTC+1, Jakub Bocheński wrote:
>
> Hi, I tried to register
> After recovering the email from my spam folder I clicked "I want to
> participate" but I get an error
>
> &
Hi, I tried to register
After recovering the email from my spam folder I clicked "I want to
participate" but I get an error
> Your participation can't be confirmed, please contact a Jenkins
administrator
Is this the right place to "contact a Jenkins administrator"?
--
You received this messag
e version number updates?
>
> Richard.
>
> On Tue, 22 Jan 2019, 2:59 AM Jakub Bocheński, > wrote:
>
>> One final thing I would ask for is to enable branch protection for
>> master; this requires admin access
>>
>> [image: Screenshot_20190121_145729.png]
>>
&
One final thing I would ask for is to enable branch protection for master;
this requires admin access
[image: Screenshot_20190121_145729.png]
On Monday, January 21, 2019 at 2:34:46 PM UTC+1, Jakub Bocheński wrote:
>
> Actually I see I now have write access. Thanks!
>
> I think w
.
Details in
https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/28
On Monday, January 21, 2019 at 2:29:34 PM UTC+1, Jakub Bocheński wrote:
>
> PPS. Just in case: I am talking about access to
> https://github.com/jenkinsci/stash-pullrequest-builder-plugin not the
PPS. Just in case: I am talking about access to
https://github.com/jenkinsci/stash-pullrequest-builder-plugin not the one
at nemccarthy/stash-pullrequest-builder-plugin
On Monday, January 21, 2019 at 1:32:13 PM UTC+1, Jakub Bocheński wrote:
>
> PS. I mean probably something is wrong wrt
PS. I mean probably something is wrong wrt those settings for
stash-pullrequest-builder-plugin repository, but having no access I can't
check:
[image: Screenshot_20190121_132945.png]
On Monday, January 21, 2019 at 1:27:16 PM UTC+1, Jakub Bocheński wrote:
>
> > Invited you agai
ub-bochenski committer on
> stash-pullrequest-builder-plugin
> [13:01] <@jenkins-adm> | Added jakub-bochenski as a GitHub committer for
> repository stash-pullrequest-builder-plugin
>
>
> Le lun. 21 janv. 2019 à 11:35, Jakub Bocheński > a écrit :
>
>> Bump?
>&
Bump?
I see only "nemcarthy" here, neither me nor @jimklimov
<https://github.com/jimklimov> is listed in
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-stash-pullrequest-builder.yml
On Friday, January 18, 2019 at 4:32:51 PM UTC+1,
stash-pullrequest-builder-plugin to jbochenski
> [17:34] <@jenkins-adm> | Default assignee set to jbochenski
>
> Le ven. 11 janv. 2019 à 17:33, Baptiste Mathus > a écrit :
>
>> Given the level of activity of the plugin (last (failed AFAICT) release 2
>> years ago),
Hi Baptiste,
I understand the concerns.
If I may suggest one improvement I would suggest ACKing the message sooner,
explaining the timeout. I wasn't sure if my email just went into peoples
spam filters or was it the holidays/new year's lull
regards,
Jakub Bocheński
On Mon, Jan 7,
PS.
> IMPORTANT: To speed up and ease the process, please provide the two
following things:
- Your GitHub id: jakub-bochenski
- Your Jenkins infrastructure account id: jbochenski
On Thursday, January 3, 2019 at 4:45:08 PM UTC+1, Jakub Bocheński wrote:
>
>
> CCing the git
> CCing the git commit email of previous maintainer.
>
> So much for that:
DNS Error: 11045696 DNS type 'mx' lookup of quanitum.com.au responded with
code NXDOMAIN
Domain name not found: quanitum.com.au
--
You received this message because you are subscribed to the Google Groups
"Jenkins De
vious bug
fixes:
https://github.com/nemccarthy/stash-pullrequest-builder-plugin/pull/149
https://issues.jenkins-ci.org/browse/JENKINS-41771
https://issues.jenkins-ci.org/browse/JENKINS-51480
https://issues.jenkins-ci.org/browse/JENKINS-55153
CCing the git commit email of previous maintainer.
Bes
Indeed I removed the hook and a build still triggered:
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Flogstash-plugin/detail/jakub-bochenski-patch-2/
There was a project-level hook for the jenkins.ci.cloudbees.com instance so
I assumed I need to update it.
Jakub Bocheński
On Thu
Another note for posterity:
Remember to update the Jenkins (GitHub plugin) service in GH project
settings to call https://ci.jenkins.io/github-webhook/
On Wednesday, July 12, 2017 at 8:19:55 PM UTC+2, Daniel Beck wrote:
>
>
> > On 12. Jul 2017, at 20:07, Jakub Bocheński > wrote:
With some detective work I found this:
https://github.com/jenkins-infra/pipeline-library/blob/master/vars/buildPlugin.groovy
Jakub Bocheński
On Wed, Jul 12, 2017 at 7:21 PM, Jakub Bocheński
wrote:
> Right, I seem to remember the announcement now -- it's a pity Jenkins only
> d
ul 2017, at 19:06, Jakub Bocheński > wrote:
> >
> > I'd be really helpful if somebody could turn it back on.
>
> As per http://jenkins.ci.cloudbees.com/ that service is deprecated, and
> has probably been disabled.
>
> Create a Jenkinsfile to have your p
Hi Guys,
I've noticed that Jenkins build result stopped appearing on PRs for
https://github.com/jenkinsci/logstash-plugin/
I think the cause of this is this project is disabled:
https://jenkins.ci.cloudbees.com/job/plugins/job/logstash-plugin/
I have no idea why this happened, the last build
Daniel,
I tried, but I get 500 ISE when trying to login to Confluence as mentioned
above
Jakub Bocheński
On Thu, Jun 8, 2017 at 6:08 PM, Daniel Beck wrote:
>
> > On 8. Jun 2017, at 17:48, Jakub Bocheński
> wrote:
> >
> > I think this should be removed now?
>
> T
I've noticed that the plugin is still marked as "Waiting for adoption" on
the wiki.
I think this should be removed now?
I tried to login, to do it myself, but I'm getting a 500 ISE when trying
to do so:
org.springframework.dao.ConcurrencyFailureException: Hibernate operation:
Could not exec
Thanks, I have write perms on GitHub now
On Mar 26, 2017 3:36 AM, "Daniel Beck" wrote:
>
> > On 23.03.2017, at 17:12, Jakub Bocheński
> wrote:
> >
> > I still have no write access there though.
>
> Should be resolved now.
>
> --
> You received t
2017 at 3:50 PM, Baptiste Mathus > wrote:
>
>> Done, welcome aboard Jakub and thanks! Thanks also Rusty for your work on
>> this one.
>>
>> @Jakub you *must* accept the GitHub invitation you should have received
>> to enable your permissions.
>>
>
Hi,
we are using a forked version of the plugin, which includes
https://github.com/jenkinsci/logstash-plugin/pull/22
I'd like to integrate that into a proper release.
If time allows I'd also like to add interruptible IO to the underlying code
as the plugin doesn't support aborting builds now (
28 matches
Mail list logo
