We are using Gitlab (7.10.2) and Redmine (3.0.2).
All issues are managed in Redmine and Gitlab manages all git-repositories.
We set up Gitlab via the UI so far that commits with the message 'Close #234' are clickable and pointing to the corresponding Redmine ticket website.
We now want to achieve that tickets in Redmine are directly linked with Gitlab commits.
If we are using the internal Gitlab issue system and set the commit-message to ‘Close #234’ the ticket 234 is automatic closed and linked with the commit.
But with Redmine as issue service system we are not able to automatic close issues with commits or have any information about this in Redmine.
Does anyone knows how we can modify Gitlab and/or Redmine to close Redmine tickets with Gitlab commits?
You can use Redmine as an issue tracker with setting the redmine service in Gitlab (In your project -> Services -> Redmine -> fill the URLs, and set active). If this works, when you press "new issue" button in Gitlab, you are redirected to Redmine new issue page. In Gitlab you should have WebHook to inform the Redmine about new push into the repo. This can be set in the settings "In your project -> Settings -> Web hooks" (how, see here).
In Redmine go to Administration -> Settings -> Repositories. Check your referencing keywords. "closes" or "close" should be in the list. Finally in the same tab there is the table at the bottom, where you choose tracker, your fixing keyword (closes, close), set applied status to "Closed", and choose the appropriate amount of % Done (100%).
Similarly you can set other keywords to change status in Redmine tickets.
Use the redmine_gitlab_hook to keep Redmine repo up-to date.
Related
Question
Is there any way to point existing Amplify apps to new repositories? Failing that, is there a way to clone Amplify app settings (including Backend environments) from one app to another?
Background
I was a complete newcomer to AWS until several months ago, when I inherited responsibility for an existing set of AWS apps developed by another team.
In our AWS account, Amplify is configured to use GitLab repositories which were under the previous team's control. I got a copy of the code, but I don't have access to the repositories.
So I uploaded the code to a new Bitbucket repository, and now I need to point the existing apps in Amplify to the new repositories. My goal is to be able to push changes to my new repository and have Amplify detect those changes so the new build can be pushed.
3 Unsuccessful Solutions
I've tried approaching this problem from a few different angles.
1. Create a new app
I created a new app which points to the new repository, which proved to be very simple. But I didn't anticipate how difficult it would be to migrate settings (especially the Backend environment) from one app to the other. So I thought it might be simpler to point the existing apps at the new repository.
2. Reconnect Repository
I thought that configuring a new repository for an existing app would be relatively straightforward. Here's the procedure I followed.
Log into AWS Console and navigate to the Amplify service
From the list of apps, select the one I want to modify
Under "App settings", select the "General" tab
Click the "Reconnect repository" button
A dialog box popped up: "Reconnect your Git repository". It prompted me to select from a dropdown list of "Recently updated repositories", but that list was empty. There's no place to enter an address for a new repository, so this path seems to be a dead end.
3. Create a Connection
I tried to "Create a connection to Bitbucket" as described in AWS documentation here: https://docs.aws.amazon.com/dtconsole/latest/userguide/connections-create-bitbucket.html
But the "Developer Tools" console seems unrelated to Amplify. The connection was created successfully, but it doesn't appear in the "Recently updated repositories" list, and I don't know how else it can be used.
If you are okay with a CLI solution, have a look at the comment below from https://github.com/aws-amplify/amplify-hosting/issues/288#issuecomment-737192995
aws amplify update-app --app-id AMPLIFY_APP_ID --repository REPOSITORY_URL --access-token ACCESS_TOKEN
... worked for me, transferring from one github account to another
github account and repo. I know it's not quite what the OP was doing,
but thought it may be worth noting that:
The AMPLIFY_APP_ID is the last bit of the app ARN (e.g.
dXXXXXXXXXXXXX)
For github repositories, the access token is a
Personal Access Token (https://github.com/settings/tokens).
I gave it all of the repo and admin:repo_hook privileges. That had to be created from the repository owner's account, not a contributor.
This helped me to change that app to point to a different GitHub repository.
AWS CLI requires some setup though, the documentation is available here https://docs.aws.amazon.com/cli/latest/userguide/getting-started-quickstart.html
Edit: You might also have to Reconnect The Repository using the UI after changing it using the CLI
I'm working with WSO2 Identity Server and I'm curious if there is a way to run the product in developer mode without building each component of identity server. I found a way to start the "My Account" component in dev mode by following this tutorial ( https://is.docs.wso2.com/en/5.11.0/develop/setting-up-my-account-in-a-dev-environment/ )
but I want to be able to modify different components such as recovery-portal and authentication-portal by forking and cloning the required github repositories and starting the entire app in developer mode in order to see the code changes in real-time.
AFAIK the developer mode will work only for the MyAccount and Console. You can refer to the doc for more details on that.
The recovery portal, the authentication portal etc. cannot be tried with the developer mode. However, there are two ways that you can try this.
Build the war files manually and add them to the WebApps directory. If the server is running, war file changes will automatically get deployed. If the server is not running, you have to delete the existing directory and restart the server.
You can do the changes to the JSPs that are deployed inside the pack. Once the changes are done, you can save the changes and the changes will automatically get deployed.
Having heard about the possibility to create and comment pull requests, I was about to try this feature:
I have successfully added by Bitbucket Cloud account in Preferences using an App Password
I can see my repository, branches
I can create branches and view changes
However, nothing related to pull requests is available:
Xcode does not detect pull requests
I have no "Create Pull Request" option in Xcode
I am using Xcode 13.2.1
Is there anything I have to set or enable for this feature to be available?
Thanks for any help in advance.
I have a redmine instance running on windows (Bitnami Redmine). I've exported the database (a dump using mysqldump).
I have a new Ubuntu Server installed on another computer with another redmine instance (just installed).
I opened a phpmyadmin session on the new Ubuntu Server, made a backup of the new redmine database and then restored the backup from my original server.
I then logged into redmine using my original server user/pwd with no problems.
I can move through projects, and issues perfectly, However, every time I press the "New Issue" option, or Settings in a project the following error appears:
Internal error
An error occurred on the page you were trying to access.
If you continue to experience problems please contact your Redmine administrator for assistance.
If you are the Redmine administrator, check your log files for details about the error.
The same if I go to "My account" or Administration -> Users or Administration -> Issues statuses.
Also, if I try to edit an existing issue, when i hit the Save button, it explodes.
Sitecore 6.6 Update 4
I've got an instance of Sitecore that is having an issue with goals. After creating (and publishing) goals, I try to assign the goal to a specific content item. When I click on the 'Analyze\Attributes\Goals' button in the ribbon, the dialog is presented, but no goals are populated in the box.
I've looked at my error logs and don't see any errors. I've watched via Fiddler and don't see anything. I've used Chrome's developer tools and see no errors.
I have another instance of Sitecore running on the same server and it has no issues populating the goals dialog box.
Any ideas?
Thanks!
Likely your goals have not been deployed to your Analytics dataset. Try pointing SQL Management Studio to your Analytics Database and issue the following:
SELECT *
FROM [Sitecore_analytics].[dbo].[PageEventDefinitions]
And make sure that the goals you are registering are actually present here. There should be a Guid in PageEventDefinitionId that matches the Sitecore Item ID of your Goal.
Okay, thanks to Mark (+1) for pointing me down a direction for solving this. This has to do with automating analytics deployment on CD servers.
Looking at section 6.2.1 of the ECM Administrator and Developers Guide, you can see that there are two tasks:
Adding the Auto Publish action
Updating the Web.config with a workflow provider for the default definition database
The goals were associated with the "Analytics Workflow", but they weren't going into a draft state after creating them and they weren't being properly deployed when saving.
After ensuring that the steps from the ECM dev guide were followed in the client's CM/CD environments, everything started working again.
Note: this may not be something someone normally sees with a default install. I had begun the process of implementing the ECM autopublish by editing the web.config files and had not completed the process of adding the "auto publish" action. Once I ensured that all items were correct, the process worked as expected.