I can not create a new agent. When I am clicking on create then it is cancelled
It could be that you are trying to use a GCP Project that already has an agent (only one agent is allowed per GCP project). Try to choose another GCP Project and see if that works.
Followed this quickstart and did not find any problem. Please, make sure that you have followed the previous steps required to create an agent: the setup and the basis.
Also, as it was commented before, each project can have at most, one agent per region.
If this path does not help, please provide me with more details about your particular situation with this agent, just bear in mind to suppress all kinds of sensitive information regarding your project and your data.
Related
I want to preface this with I tried to submit this in the developercommuinty.visualstudio.com Request a feature section and it wouldn't upload due to server errors, 403 and bad requests.
On-prem DevOps version: Server 2020 (18.170.30331.4)
Scenario
I was going through some code with another team as they were asking questions it. The code in question was connecting to a database and then querying a different database. So now, a bug has been identified and I was looking to create one that calls out this specific line of code. When highlighting it in the repo and right clicking, there wasn't a way to create a task from it.
Expectation
I was expecting a similar experience to what GitHub has and create a work item that points to the specific line of code.
Suggestion
Mirror that similar functionality from GitHub in Azure DevOps when selecting lines in the repo and being able to create a work item from it.
It's the first time I make a pipeline for CI/CD in Gitlab. At a point, when registering the runner, we can "Enter optional maintenance note for the runner".
I looked for more information about it, but I found nothing in GitLab documentation except for Admin Notes and the example in the issue to add Optional Maintenance Note does not really help me to understand.
So, what is the purpose of the optional maintenance note ?
When do we need to look at this message ?
In the issue, they said it is not for casual user, so is it dedicated only for developers ?
Also, can you give me an example of what an optional message can be ?
Thanks !
The GitLab issue you linked, I think, answers the question.
The Maintenance Note field would contain information relevant to other developers managing this GitLab Runner. e.g. - What machine does it run on, how many cores, how much ram, what OS? Basically, any information about this specific GitLab Runner instance you think would be relevant to share with other devs on this project.
It's perfectly fine to leave this field blank.
I'm wanting to add some test case attachments during a build or release but I'm struggling to find a valid approach to do this. I'm not using MSTest.
I tried creating a custom build/release task but I've found the azure-devops-node-api package to be flaky at best, and seemingly lacking contributors.
This is what I would hope to do...
Use C# if possible
Have the code/task available for either a build or release across multiple repositories and projects (same organization) without code duplication
Automatically authenticate with the currently running build/release without needing PAT tokens or any other form of authentication
Access to both Azure File Storage and Azure Devops
Works with any build or release agent
Is this achievable? I've seen odd articles in various places but nothing like whats described above. For example this shows promise in terms of validating the current build/release in a C# application however it is 4 years old now and doesn't explain how to integrate with a pipeline.
Can anyone help?
Thanks,
I've always leveraged mstest, so within the runner we've had access in c# to the TestContext that supports adding the attachements directly to the test result.
It looks like the API is exposed for adding attachments to the runs though, so I would think you can create something either in c# or in powershell that accomplishes what you are asking. You will likely need to make sure the agent phase has access to the OAuth token.
POST https://dev.azure.com/{organization}/{project}/_apis/test/Runs/{runId}/Results/{testCaseResultId}/attachments?api-version=5.1-preview.1
I have been trying to create a simple Probot app that amongst other things will merge PRs on certain criteria being met. (I am aware prebuilt solutions are available, however not only do they not quite fit my needs, I won't learn anything).
Using context.github.pulls.merge(context.issue()) returns: ERROR probot: Resource not accessible by integration
I have tried replacing context.issue() with the object the docs suggest its looking for.
Googling although difficult to find similar issues, suggest its a permission issue, I have double checked the permissions and at one stage given the app every permission.
Things worth noting:
There are no github actions setup on this repo
The repo belongs to a testing org, the bot app has access to all repos in the org
The repo was initially private, but have also tested in public
Any nudge in the right direction will be greatly appreciated.
Thanks
I see it has been quite a while since you posted this question.
You should not be using context.github.pulls.merge(context.issue()) in the first place. This will never work given the signature of the actual merge method(). You said you have tried following the doc's suggestion.
Is this the doc you are referring to?
The doc clearly suggests to provide owner, repo and pull_number to context.github.pulls.merge().
Did you try that? Please dod share your findings.
I have just a single instance of jenkins on a local machine which we are using to build our code. We have different project teams working on different projects, and different jobs for each project.
To eliminate the possibility of someone from one team accidentally messing up another team's job, i have created multiple jenkins users.
However, all of the users that can log on still see all of the jobs. Is there a way for certain users to only see the jobs that pertain to them?
I have searched extensively for something like this but no luck. I haven't found any plugins for this. I am using matrix based security currently, and although you can change the permissions of all the users through this, you can not apply specific permissions to specific jobs. At least to my knowledge. Any ideas?
Just to clarify, I want one of the many teams to log in to their user account in jenkins, and only see their jobs. The jobs of the other teams should not be visible, only the ones that they are assigned should be visible when they log on
The closest thing i have found for this is in the Role Strategy Plugin, there is a user-based job filter
Turns out there is a feature already in jenkins for this, no plugins necessary!
In the Configure Global Security section in Manage Jenkins, click "Project-based matrix authorization strategy".
Then you can configure permissions in the job configure screen for that particular job by clicking "enable project-based security".
Now you can configure your Jenkins so that "Joe can access project A, B, and C but he can't see D".