How a commit message can be displayed on both issue details and email notification? Regarding the issue notification, I know I've had it already up and running, but it stop working without apparent reason. For now, the only information which is displayed regarding the commit is the related changeset in the History section.
Thanks in advance for the help,
Best regards!
I think I already know which the problem was; the project in question is a sub-project from a main project and thus, is not possible to associated each revision with a specific issue.
Related
I did some version changes in my project and commit those. But I cannot Sync those and push to the server. SO that I cannot make a pull request in bitbucket?
I am using Visual studio 2017
It Shows the error message"Failed to push to the remote repository. See the Output window for more details."
In the out window, it display "One of your commit messages is missing a valid issue key:"
Can any one please help me? I am new to this.
The actual error message is:
One of your commit messages is missing a valid issue key:
Most likely, this is being caused by either a client or server side Git hook. The fix here is probably to check the commits you have made since last pulling the branch, and verify that each one has an issue key/number.
As to why the Git hook is ensuring that each commit has an issue key, it is to ensure that your commit history can easily be correlated with your team's issue tracker tool (such as Jira or Trello).
I found a solution for my above problem.
In there it displayed a Error message called "One of your commit messages is missing a valid issue key".
For solve this I click on my current working branch and go to "View History". Then you can see all the commit messages and your branch history in Visual Studio.
Then you should identify which commit have the issue. Some times it may be a space in your gira task id.
Then double click on the comment that have the issue.If it is your lastly updated commit then you can directly edit that commit message and click on "ammend message".Then your commit is again in the changes tab in your Visual studio.
If it is not your lastly update commit then you have to click on the "Reset" "Reset and keep changes" and refresh your history tab in your visual studio until the issue comment become the first. Then you can edit the commit message and "ammend" it.
I went here and started on the first task which is to create a registry. I later closed my browser and when I go back to that page, I just get the homepage again and if I start that wizard, it acts as if I've never done it before and forces me to create a new repository.
How the heck do I get back to the repository I created initially and then how can I continue on with this wizard to the next steps with that repo? Or do I lose the repo entirely until I get through all steps in this wizard? Where the heck did my repo go? It says it exists but where? How do I get to back to that repo on the AWS control panel?
https://console.aws.amazon.com/ecs/home?region=us-east-1#/repositories
no? I couldn't comment instead of posting as answer due to insufficient reputation, sorry for that.
For last two updates of Glass (XE19.* and XE20*), whenever I load my Glass app onto a device it seems to get auto-deleted after a few hours. Has anyone else noticed this behavior and have a workaround to prevent it?
This question seems to indicate that if your apk has the same package name as one that is going through the review process, that it may be removed. Use a package name that is different or go through the review and whitelist process.
Update: The whitelist process allows you to permit a select group of people to be able to access the apks as you update them while they are being reviewed. You should be able to ask the review team about this once the process is underway.
I started a job as a web developer at a company a few months ago managing a bunch of Coldfusion applications among other things. Apparently a scheduled task was set up many years ago, and worked fine until it stopped working under one of the previous web developers, a couple of years ago. No one knows why it stopped working, but it is now my job to fix it. This is my first job as a web developer, I didn't know CF when I started my job (barely knew it existed), and I only started learning about scheduled tasks this morning, so just know that I am a total newbie.
The file is a basic one- it just updates a table in the database. If you run the URL in the browser (which is what they have been doing for the past couple of years), it runs fine, and everything is updated. The scheduled task, which was set to run every night, has not been updating the file. I've tried turning on the log in CF Admin, setting it to run at various times this morning, and also just telling it to run manually, and according to the log, it is executing (with no errors), but the file is not being updated. I tried commenting out most of the file and just telling it to send a basic e-mail, with no variables or anything, but I am getting the same result.
Any ideas? I have no idea what to try from here. I tried looking for a solution online, but the only post I found similar to my situation is this, where people seem to be suggesting that the issue may be variables that are not available to the scheduler:
coldfusion scheduled task not sending emails
There are no variables on my page right now though. I tried running the task via CFSCHEDULE, per the suggestion on that page, but I got the same result as before. Some of the other suggestions (server monitor/FusionReactor/cflog) I just plain don't know how to do, so I have not tried those.
Edit: Right now, this is the only code in the page which is not commented out:
<cfmail
to="[e-mail address]"
from="[e-mail address]"
Subject="is it running at all?">
Is it running?
</cfmail>
Edit 2: Okay, now I've got something like this before and after the code for the e-mail:
<cflog
text = "before e-mail"
application = "yes"
log = "Scheduler"
type = "information">
I see the log messages if I actually go to the URL for the file (and the e-mail is sent as well), but not if I tell it to run the scheduled task from CF admin. Because the e-mail sends when I open the file in the browser, I don't think it is a problem with the mail server.
Edit 3: Yes, the e-mail addresses are plain, hard-coded strings.
I'm not exactly sure what you mean by "covered" by an Application.cfm file though. There is an Application.cfm file in the top-level of the site, but not within this particular sub-directory. There are a number of Application scope variables, but none that are used in the file as it is now.
Edit 4: Thank you for the explanation. As I said, total n00b when it comes to CF, so I appreciate the help. The Application.cfm page for this application checks to see if you are logged in, and if you are not, redirects you to the log in page. Could that be the issue?
Edit 5: YAY! It seems like that was the issue. Thank you thank you thank you! Leigh, please submit that as an answer so that I can choose it. You are my hero!
(From the comments )
A long shot but is your scheduled task inside a directory covered by an Application.cfm/Application.cfc file? The reason for asking is that the code inside the parent Application.cfm file executes first before your .cfm script. Is there any code inside the Application.cfm file that aborts a request or redirects (such as permissions check)?
What is the great motivation behind integrating Redmine with a source control repository ? If it is only for monitoring reason, developers already have access to repository and they can do whatever they want diff, history with their IDE. For other people do they really need? I'm afraid, I can't see the real reason. Can you please help me to see ?
When you fix a bug that exists in Redmine's issue tracker, you can refer to the issue id in the commit message and Redmine will automatically associate the commit with the issue (or even close the issue).
This saves you the double work of referring the issue in the commit message and closing the issue in Redmine.
By the way, this is not Redmine-specific - you can do it with most bug trackers that offer source control integration.
I don't remember the exact syntax in Redmine right now, but most of the time, the syntax is something like:
fixes #123
...which would cause Redmine to automatically close issue #123, and create a link from the issue to the commit (and vice-versa).