OrchardCMS / OrchardCMS/Orchard

Reduce CodeBetter CI usage for nightly builds

Open
#4,635 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

task
Dominant language
C#
Stars
2.4k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

adamralph created:
https://orchard.codeplex.com/workitem/20806

Currently, the nightly build is using 2 hours on JetBrains-agent01 at CodeBetter CI http://teamcity.codebetter.com/viewType.html?buildTypeId=bt539.

Given there are over 200 projects configured to use this single agent (http://teamcity.codebetter.com/agentDetails.html?id=7&agentTypeId=7) it would be greatly appreciated if this level of usage could be reduced to a fair level. If all 200 projects had 2 hour nightly builds we'd be pretty stuck.

I work on a few of these other projects (the longest build takes 6 minutes) and work has been blocked a few times now for up to two hours whilst waiting for the Orchard nightly build to complete. I guess either the nightly build needs to be changed to do less, or it should be moved to a dedicated server/agent.

I'm not sure if CodeBetter CI has a fair usage policy but I'm sure as a community we can work things out regardless.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the nightly build configured as CodeBetter CI build type bt539 and its use of JetBrains-agent01, as linked in the issue. The issue does not name repository files or tests; done means reducing the nightly build's agent usage or moving it to a dedicated server without blocking other projects.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
build-system, ci-cd
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.