Has anyone experienced the Aggregator job reporting that it has run, but no
result coming out of it? I have a pipeline that runs at the same time daily
and the end of that pipeline is the Aggregator job. The Aggregator
indicates success, but no email is being sent out.
Thoughts? Advice?
--
Yo
I may have stumbled across the solution to a different conversation that I
posted. I noticed that the number of recipients I include in the Recipients
list of the Aggregator may be causing me trouble. Would someone be willing
to test this hypothesis on their side, too?
I have included 1 email r
ns/testresultsaggregator/reporter/MailNotification.java
> webde...@gmail.com schrieb am Dienstag, 16. März 2021 um 20:33:01 UTC+1:
>
>> I may have stumbled across the solution to a different conversation that
>> I posted. I noticed that the number of recipients I include in the
>
currently, there are no errors in the console output from the job. the job
marks itself as a success
On Friday, March 19, 2021 at 11:52:11 AM UTC-5 webde...@gmail.com wrote:
> thank you for this feedback. it will help me resolve this issue!
>
> On Wednesday, March 17, 2021 at 2:08:32
I can't find any good documentation regarding the Repository Depth and its
infinity setting. Can anybody connect me with the documentation they read
to more fully understand this item in Jenkins?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group
good morning, all. My team and I have hit this issue before on the same
node/agent and a reboot "fixed" the issue, but we ran into the issue again
this morning on the same node.
here's the specific error:
org.jenkinsci.plugins.workflow.steps.MissingContextVariableException:
Required context cl
Hey, all,
Found this error in the System Log and I'm unsure how to resolve. This is a
follow-up to this issue I mentioned earlier:
https://groups.google.com/u/1/g/jenkinsci-users/c/kNbAmi85ZI8
Error Message:
falling back to default instantiation
com.jenkins.testresultsaggregator.data.Data
{
Hey, all. My team updated our development server on Friday to 2.277.1 and
ever since then, when I attempt to Save a job pertaining to the Test
Results Aggregator, I can't. When I add information to fields within the
job and then attempt to navigate away from the job, I get the alert
informing m
Bit of a doozy in this one. I have a pipeline within a folder structure. I
made a copy of that folder so that all the jobs would come over and I would
not have to touch the jobs except to target servers, change config files,
and modify ps1 files. The pipeline that this pipeline is copied from ru
2 PM UTC-5 webde...@gmail.com wrote:
> Bit of a doozy in this one. I have a pipeline within a folder structure. I
> made a copy of that folder so that all the jobs would come over and I would
> not have to touch the jobs except to target servers, change config files,
> and modify ps1 fi
hey, all!
Here's what I would like to do:
1. in the pipeline itself, create an environment variable.
2. pass that environment variable to a job
3. that job will overwrite the environment variable's value at the top level
4. a later job will use this new value within its execution.
something like
jochen@gmail.com schrieb am Donnerstag, 15. April 2021 um 09:35:53
> UTC+2:
>
>> How about writing the value to a temporary file instead? A shell
>> script could use the file later on (in another stage) to set the
>> environment variable.
>>
>> On Wed, Apr
12 matches
Mail list logo
