I'd like to create one tasks report for all projects. As the avilable option you can creat trackers report for every project individual.
Related
I have several GitHub actions created with workflow *.yml files. They run automated tests.
On each scheduled run of these workflows, I need to get some properties from the current workflow from my node.js code that is running. For example name.
How do I do that?
I am using GitLab for Git version control and GitLab CI / CD for my automated builds. Usually, the builds are triggered by Git repository activity but I also have a weekly build to ensure that projects not under active development continue to work. When there is only a "master" branch on a project, it is easy to ensure a weekly build is run on the latest code. When there are multiple branches in a project, I would like to repeat the pipeline work for each of them in turn.
What I would like to be able to do is schedule a build (weekly, fortnightly or monthly) that runs on all current branches visible in Git. Is that possible within GitLab's Continuous Delivery system?
The motivation behind doing this is to ensure that external activity, such as tool and library updates, do not introduce an issue without it being promptly visible. Assuming there are reasonable automated testing, coverage and comprehensive builds for target platforms, a monthly build with the latest tools should highlight the problem promptly. This is better than an invisible mountain to problems accumulating while a project is shelved for a few years (or months). Sometimes all that is required is occasional maintenance.
There are only a handful of feature branches and release lines on the projects currently. I would not expect that number to grow significantly. There is time enough over a weekend to run the required pipelines dozens if not hundreds of times at present.
Ideally, I would like something straightforward to set up. I cannot see anything in the admin GUI that would allow this at present. I did look at the API and I can see there is some scope there to script the addition and removal. Perhaps some script that is run once a month to create new Scheduled pipelines based on git branches is the only way. A pre-made solution on those lines would be perfectly acceptable. If nothing exists I might start work on something like that in time.
I am currently running GitLab Community Edition 11.2.3 06cbee3 (GitLab CE 11.2.3). If there is an Enterprise Edition only answer, that is fine and will add to the justifications of purchasing the EE version. I would pick at CE one above the EE one though.
You cannot set a schedule for all branches at once, you have to configure one schedule per branch yourself.
Perhaps some script that is run once a month to create new Scheduled
pipelines based on git branches is the only way.
I would go in that way.
I'm new to the azure webjob. I have multiple jobs that I hope run at a different frequency. As for now, my solution is to have one single webjob as a standalone project and define the frequency of this job at project level, in the settings.job file.
However, not sure if there is a way to have multiple jobs in the same project and we can have a one time deployment of a single project, yet have each job running at different frequency?
I looked up online, the closest one that I can find is this page, which doesn't seems to work for me. Any help/sample code is appreciated.
To achieve this, we can create a settings.job file in root folder of each web job project as below.
Notice, we need to choose "Copy always" as below
More information about settings.job file, we can refer to: Web Job Types
A quick Google search shows all sorts of options for pre & post build events but none seem to cover building multiple projects.
In my solution I have over 100 different projects (literally not an exaggeration) but at any one time I am only working one or two.
Often the two, three etc. being worked on have some connection and so changes to one means all three need to be rebuilt.
Rebuild ALL works but it takes minutes not seconds for all 100+ project to rebuild. Rebuild of just the one only works for the one.
Is there a way in pre build or post build to specify building another project(s).
The thought is when working for a week on say two projects I would specify in post build to also build project X.
Thanks
Open Project - Project Dependecies dialog in Visual Studio and fill dependencies for every project. This should give you desired effect, istead of using Post Build event.
I would like to have two (or more) different triggers for different tasks in one project. Is this possible?
For example:
A interval Trigger to build my project ones an hour and a scheduled trigger to perform my unit test once every day.
I'm using the latest version of CCNet with MSBuild and MSTest.
Okay, I solved it by myself and did it in two projects in the ccnet.config.
Each project has its own trigger and performs one task (build or unit test).