For a regulatory requirement, we are supposed to show the previous versions of a page/asset (state of page as of particular date) at publish instance. So when an end user searches an asset, and if the asset had multiple versions, he should be able to hit any version from the search result.
I managed this to solution from author instance wherein I included the versionId in query param or selector and a custom filter picked this version in url, used version manager to return the respective version of page.
When it comes to publish, from 6.1 AEM has made ACLs stricter in accessing /jcr:system. I tried to publish a revision say /jcr:system/jcr:versionStorage/1f/4f/d1/1f4fd128-b9e3-43cc-9d8a-9335bb34c3ae from activation tree and it didnt publish either.
With this requirement how can we publish versions of a page/asset?
Related
GitHub's Actions feature recently started letting users generate badges, to showcase the status of their tests. For example, if I have a set of tests that run on my repo's dev branch from a file named .github/test_dev.yml, I can access that build's status by adding /badge.svg to the end of the test's URL.
https://github.com/<username>/<repo_name>/actions/workflows/test_dev.yml/badge.svg
That's great from the standpoint of keeping your project readme up to date with the status of the project, but the next logical step would be to also add a link to the badge that points to the latest testing outcome.
Unfortunately, even though you can access all the tests of a particular action as follows:
https://github.com/<username>/<repo_name>/actions/workflows/test_dev.yml
The test runs themselves seem to be behind a unique ID under actions/runs/.
https://github.com/<username>/<repo_name>/actions/runs/1234567890
Is there any way to construct a URL that just points to the latest test? Something like:
https://github.com/<username>/<repo_name>/actions/workflows/test_dev.yml?result=latest
I poked through GitHub's documentation, but even though there's some documentation surrounding the generation of those badge SVG's, I couldn't find anything about linking directly to the action that actually generated that SVG.
you can use this to get the id in a yaml file:
https://github.com/<username>/<repo_name>/actions/runs/${{ github.run_id }}
I currently use these tools :
Azure DevOps - Only for Git repositories
Jira - To manage tasks / bugs / versions / customer requests / ...
TeamCity - Continuous integration (build and deploy versions )
I would like to replace Jira with Azure Devops (but continue to use TeamCity for builds for now.)
I already created some teams / areas / user stories / bugs.
But I would like a simple way to handle versions. For example, I fix some bugs and release a new version using TeamCity (ex. : v3.1.1.1234 ). How can I update my user stories / bugs to say that it is fix in this version ? There is no "Fix version" field like in Jira...
Should I use "Iterations" or just "tags" ?
If I want to generate release notes for the new version (for internal use), do I have to use Azure DevOps queries ?
You can create a customized field (ie.Fix version) for User Stories in azure devops. You can follow below steps:
1, Create an inherited process. (only an inherited process is allowed to create custom field)
Organization Setting--> Process under Boards--> Select the Process--> Click 3dots(...)-->Click Create inherit process.
2, Create customized Field for the inherited processs which created above
Choose your inherited process, and then choose the Work Item Type (ie, User Story)you want to customize.
Click New field, type in the new field's name (ie. Fix Version) in the Definition section. (you can decide where the new field should locate in Layout section or keep the default layout).
3, Change your project process to above inherited process.
Choose the process that contains you project. Click Projects-->Choose your Project-->Click the 3dots-->Click Change Process
You can check the document here for more information.
After you finish above steps, you will see the new field Fix Version in User Stories edit page.
If you find above steps complicated, you can just use tags.
#Levi Lu-MSFT, This only lets you create field in one workitem type if you want same field in Bugs, Features, Stories it wouldn't allow, it'll throw 'Field already exists" error.
I am developing web extension for VSTS. I am using vss sdk of Microsoft.
I got some issue.
You can see on the image that there is new line - App insights Settings
This pop up appears on clicking on 3 dots near every release definition on page of list of all releases.
This button navigates user to some environment of some specific release.
Example of link:
https://ozcodedev.visualstudio.com/OzCode/_releaseProgress?releaseId=372&_a=release-environment-logs&environmentId=850
The problem that I do not know how to fetch list of releases and environments for building this link.
How can I get them on page All release pipelines.
Through the GUI it is not possible to get all the release ids and the environment ids for each step. However this is possible through the VSTS APIS. You could use the release endpoint to and iterate to obtain your release id
https://{accountName}.vsrm.visualstudio.com/{project}/_apis/release/releases?api-version=4.1-preview.6
Once you have the release id you can use it like so
https://{accountName}.vsrm.visualstudio.com/{project}/_apis/release/releases/{releaseId}?api-version=4.1-preview.6
Within the returned JSON you can follow iterate the path environment[n].id to obtain the environment id.
You can then construct the link using this information.
Hope that helps
Ok. So after working 2 days on this issue I found solution.
1.It is possible to fetch data that I wanted on Client Side. For this I used Microsoft's library vss-web-extension-sdk. Install it - npm install vss-web-extension-sd --save.
2.Add relevant scopes to your vss-extension.json. In my case the problem was - that I needed data that relates to managing of VSTS user releases. So after Including "vso.release_manage" to my scopes array I stopped to got 401 Unauthorized error because access token was changed according to new scopes.
https://learn.microsoft.com/en-us/vsts/extend/develop/manifest?view=vsts#scopes
In this documentation you can check which scope controls which resources that can be accessed by your extension.
You can use our ts/js clients to get whatever you want for your experience.
We have extensive documentation available here. Let me know if you are blocked anywhere.
I am working on VSTS/TFS extension development work.I am trying to determine the name of current process template (whether Agile, CMMI, Scrum) via TypeScript code.
My requirement is updating workitem (bug, issue .etc.) status according to certain conditions. For same I need to identify prevalent process template name of the project. Reason is same workitem type in different templates have different status.
I am referring vsts-node-API to achieve this task. But I still couldn't figure out the way to fulfill this.
references:
https://github.com/Microsoft/vsts-node-api
https://www.visualstudio.com/en-us/docs/integrate/api/wit/templates
The response of rest api Get a team project can return "processTemplate" parameter:
GET https://{instance}/DefaultCollection/_apis/projects/{project}?api-version={version}[&includeCapabilities={boolean}&includeHistory={boolean}]
I have created a REST project in yii2 and i have some yaml data that should be stored in the database. These are crowd data, that is authorized people can add new yaml files and our app will parse those data and store in database.
But these data might change in the future (i.e. add/delete columns) which would rely on version of the REST api (v1.0, v2.0 etc)
Thus i would like to call the appropriate rest action to do it.
I know there is the function $controller->run() but how do i use it to make a POST or a PUT request?
Is there any alternative to using yii httpclient?
Thanks
If I am not wrong, you want to execute different action depending on the version of the API.
For that, you can create modules inside your frontend/backend directory and name the modules as per your versions. Whenever you have a new version create a new module and upgrade the version name. Thus you always get the proper versioning. So v1, v2.. will be modules in your project.
The good thing about this is that you can have same action name in different modules under same controller name. Thus if in version 1 you have 5 columns and the api is like /v1/data then you can have 7 columns in version 2 and the api can be like /v2/data.
For more details on modules: http://www.yiiframework.com/doc-2.0/guide-structure-modules.html