Yes, as already mentioned there are at least 10 ways how you can do
it. all depends of your project. As general approach after all jobs
finished you should have all artifacts uploaded to server as Test
artifacts. you need to figure out stage, jobs, task organization which
is needed as best solution. Then check in server artifact storage and
you will find all your files there. So just create one html summary
report file and put it in place( custom tab).  Look in folders what
you can find more and use that, as not only your artifacts are stored
there. :-)
Involve your imagination to solve it( devops approach). Till now I did
not find situation which GOCD is not able to solve.

Best Regards

2020-08-05 16:50 GMT+02:00, go-cd@googlegroups.com <go-cd@googlegroups.com>:
> =============================================================================
> Today's topic summary
> =============================================================================
>
> Group: go-cd@googlegroups.com
> Url:
>
> https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/go-cd/topics
>
>
>   - Can anyone help me with the steps to get reports in custom tab from all
> jobs running in parallel in one stage, AS i have noticed i am getting report
> only for 1 stage and other stage reports are lost. I have created custom tab
> for report [2 Updates]
>     http://groups.google.com/group/go-cd/t/4466803cf00ef669
>   - GoCD - Deploy using an artefact rather using git checkout - URGENT
> please [3 Updates]
>     http://groups.google.com/group/go-cd/t/2de8e6ec20a027f4
>   - Performance Issue in GoCD [1 Update]
>     http://groups.google.com/group/go-cd/t/3cb3b225389d7297
>
>
> =============================================================================
> Topic: Can anyone help me with the steps to get reports in custom tab from
> all jobs running in parallel in one stage, AS i have noticed i am getting
> report only for 1 stage and other stage reports are lost. I have created
> custom tab for report
> Url: http://groups.google.com/group/go-cd/t/4466803cf00ef669
> =============================================================================
>
> ---------- 1 of 2 ----------
> From: Sunaina Awadhiya <s.sawadh...@gmail.com>
> Date: Aug 05 03:42PM +0530
> Url: http://groups.google.com/group/go-cd/msg/56defc815de96
>
> Thanks Sim,
>
> Really helpful information. I did create different folder path for html
> report for 2 separate jobs which are executing in parallel and i have got
> html reports successfully for both jobs but most of the times only 1 job
> return html report. So just curious to know what could be the reason behind
> and can you please help me how to merge all jobs report and put in one
> single html.
>
> More detail steps with example would be more helpful.
>
> Thanks and Regards,
> Sunaina
>
>
> --
> Sunaina Awadhiya
> Bangalore
>
>
> ---------- 2 of 2 ----------
> From: Jason Smyth <jsm...@scimarketview.com>
> Date: Aug 05 06:37AM -0700
> Url: http://groups.google.com/group/go-cd/msg/4f43d72458176
>
> Hi Sunaina,
>
> If you want to merge the HTML reports from multiple GoCD Jobs into a single
>
> HTML document, you will need a process that runs after all of the relevant
> Jobs has completed.
>
> The simplest way to accomplish this in GoCD is to add a new Stage that can
> consume the artifacts generated in the previous Stage:
>
>    1. Stage 1: Do stuff in multiple Jobs. Generate multiple HTML reports.
>    2. Stage 2: Merge HTML reports from Stage 1.
>
> Another way to accomplish this is to add a Job to the existing Stage where
> the first Task is to wait for all other Jobs in the Stage to complete:
>
>    1. Job 1:
>    1. Task 1: Do stuff
>       2. Task 2: Create HTML report
>       2. Job 2:
>    1. Task 1: Do stuff
>       2. Task 2: Create HTML report
>       3. Job 3:
>    1. Task 1: Wait for all other Jobs to complete
>       2. Task 2: Merge HTML reports from all other Jobs
>
> There are some downsides to this approach. Job 3 will often have a much
> longer runtime than is required to do its work. If you're not using Elastic
>
> Agents this means that Job 3 needlessly ties up one of your Agents while
> waiting for the other Jobs to complete. Depending on the specifics of your
> GoCD infrastructure configuration, it is even possible for Jobs to be
> scheduled in such a way that the Pipeline Stage gets blocked. Imagine this
> as a Template in a setup with just 2 static Agents and 2 Pipelines based on
>
> this Template. It is possible, in this scenario, that Pipeline 1 Job 3 gets
>
> started on Agent 1 and Pipeline 2 Job 3 gets started on Agent 2 before Job
> 1/2 from either Pipeline, resulting in both Pipelines being blocked as Job
> 3 runs forever waiting for the other Jobs to finish and the other Jobs
> stuck waiting for an Agent on which they can run.
>
> A third way to do it is to add a Task to end of each Job that does the
> merge work if it is the last Job running for the Stage:
>
>    1. Job 1:
>       1. Task 1: Do stuff
>       2. Task 2: Generate HTML report
>       3. Task 3: Am I the only unfinished Job? If yes, merge all reports.
>    2. Job 2:
>       1. Task 1: Do stuff
>       2. Task 2: Generate HTML report
>       3. Task 3: Am I the only unfinished Job? If yes, merge all reports.
>    3. ...
>    4. Job N:
>       1. Task 1: Do stuff
>       2. Task 2: Generate HTML report
>       3. Task 3: Am I the only unfinished Job? If yes, merge all reports.
>
> This solution is subject to race conditions, though, because GoCD Jobs do
> not complete until all Artifacts have been uploaded and Artifacts are not
> uploaded until after all Tasks complete. This means that it is possible for
>
> the last Job to run its "am I the last?" check while the second-to-last Job
>
> is still uploading Artifacts. If this happens then the last Job will not
> recognize that it is the last one and will not run the HTML merge task.
>
> Hope this helps.
>
> Regards,
> Jason
>
>
> On Wednesday, 5 August 2020 06:13:08 UTC-4, Sunaina Awadhiya wrote:
>
>
>
> =============================================================================
> Topic: GoCD - Deploy using an artefact rather using git checkout - URGENT
> please
> Url: http://groups.google.com/group/go-cd/t/2de8e6ec20a027f4
> =============================================================================
>
> ---------- 1 of 3 ----------
> From: Prakash Tirumalareddy <tiruma...@gmail.com>
> Date: Aug 05 12:41AM -0700
> Url: http://groups.google.com/group/go-cd/msg/565abb39a5d04
>
> Hello Everyone
>
> Is there anyway we can configure a particular stage not to do git-checkout
> and instead download the artefacts from external repository (such jfrog
> artifactory) which was built and pushed in previous stage?
>
> Currently what have seen that at every stage it does the git-checkout for
> the commit hash.
> I know there is a stage configuration which says not to checkout the
> material. But when we enable this option then there is no way in that stage
>
> to do required task.
>
> Your help will be greatly appreciated.
>
> Regards
> Prakash
>
>
> ---------- 2 of 3 ----------
> From: Helge Walter <bewalti...@gmail.com>
> Date: Aug 05 01:40AM -0700
> Url: http://groups.google.com/group/go-cd/msg/4e40784c911b8
>
> Hello Prakash,
>
> there are 2 ways to achieve this:
> 1. You can store the created artifact from the previous stage as a
> resulting artifact (
> https://docs.gocd.org/20.4.0/configuration/managing_artifacts_and_reports.html)
>
> and then fetch the artifact in the next stage with the "Fetch Artifact"
> task for further use.
> 2. Upload the artifact to the Artifactory in the previous stage and
> retrieve the artifact in next stage using a simple curl task.
> I would prefer the first option because all the artifact handling is done
> by GoCD internally.
>
> Regards,
> Helge
>
> Am Mittwoch, 5. August 2020 09:41:40 UTC+2 schrieb Prakash Tirumalareddy:
>
>
> ---------- 3 of 3 ----------
> From: Prakash Tirumalareddy <tiruma...@gmail.com>
> Date: Aug 05 03:14AM -0700
> Url: http://groups.google.com/group/go-cd/msg/56dfebf2e327b
>
> Hello Helge
>
> Thanks for your kind reply.
> Either of the option is not solving the git-checkout at every stage.
> Is there way we can achieve to run stage by executing download the
> artefacts from Artifactory. (Can we put curl command in the pipeline.yaml
> itself? if so can you please give me some example?)
> Thanks again!!!
>
> Regards
> Prakash
>
>
>
>
>
> =============================================================================
> Topic: Performance Issue in GoCD
> Url: http://groups.google.com/group/go-cd/t/3cb3b225389d7297
> =============================================================================
>
> ---------- 1 of 1 ----------
> From: Bala s <write2ba...@gmail.com>
> Date: Aug 05 12:38AM -0700
> Url: http://groups.google.com/group/go-cd/msg/4e0ae940db866
>
> All, Any suggestions?
>
> Thanks,
> Bala
>
> On Wednesday, July 29, 2020 at 4:57:01 PM UTC+5:30, Bala s wrote:
>
>
>
>
>
>
> --
> You received this digest because you're subscribed to updates for this
> group. You can change your settings on the group membership page:
>
> https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/go-cd/join
> .
> To unsubscribe from this group and stop receiving emails from it send an
> email to go-cd+unsubscr...@googlegroups.com.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA%2BdczRoiXuvhOcXZFfjYjGCMRhTu_1A1-uj66YPN_eS1ttDJQ%40mail.gmail.com.

Reply via email to