How I can update all/several snapshot in WebStorm?
I only have 1 button that updates snapshot, then I have to re-run tests and it’s not convenient.
Not currently possible. Please vote for WEB-33822 to be notified on any progress with this feature
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.
In the new Qubole Analyze UI that came out recently, I cannot seem to find a way to change the title of a command. In the old interface, I could click on the command title and it would become an editable text box.
We are not planning for the same feature of having to edit command names. But the similar will be available as part of collections feature which is currently work in progress. We will update our release docs as it is ready for release.
I'm working on implementing a three step workflow for my company's Sitecore 8.2 installation.
Originally I had the final step set up to not have any action or command because we want to manually publish. But, manually publishing does not seem to remove the final workflow state.
Screenshot of the items workflow state after manually publishing
Then when I edit the item, it doesn't move back to the draft state. It's my understanding that when you publish an item that made it to the final workflow state version 1 is created, and editing that item should create a new version and restart the workflow. Is this correct?
After realizing that manually publishing does nothing, I tried setting up a command and action on the final workflow step:
Screenshot of final workflow step command & action
But this does nothing. Is it possible to set up a workflow action to publish? Or is the out of box auto-publish action the only option?
Why are the items getting stuck in this final step and how do I fix this?
Edit: The workflow was getting stuck because I am an admin. When using the roles I set up for Content Author and Approver, I was finally able to get the item to start version 2. I would still like to know if it's possible to set up a command and action to publish? Or is this not necessary if we want to manually publish anyway?
I think i know the issue. I had similar issue while setting up my sitecore workflow and i solved it with some changes in the security settings.
I wrote a blog just now about how to setup Sitecore Workflow. Here is the link for that:
https://tectraveleat.wordpress.com/2018/06/01/sitecore-workflow-setup-v8u2-v9-0-1/
In your case, since you have already setup everything. You might want to take a look at the "Assign security permissions to the roles" section of the blog.
Also, it is necessary to give the roles/users permissions to the datasource. From what i understand, you have setup everything properly, except a minor security permission at the workflow level.
Let me know if this helps. If not, can you share your workflow setup and permissions for the roles? I can take a look at it and see it i can help.
You can follow sample workflow of sitecore. Workflow publish state is final state. It can not move to draft. This process of workflow like this: Draft -> Approved -> Published. Workflow done at here.
If you wanna create version or make page to draft you have to edit it. If you still wanna your page published -> draft, you can custom pipeline of command in workflow. But this solution have many risks, I asked Sitecore support before and they answer it just their logic and you can custom if you want.
Using Visual Studio 2017 with Data Lake Tools v. 2.3.1000.1, I am unable to submit a U-SQL job directly to Azure. I only have the option to submit locally:
This is the case even though I am connected to Azure through the "Server Explorer" tool window, from which I can access my U-SQL databases, view jobs that were previously submitted to Azure, etc.:
Using Visual Studio 2015, I have no such issue:
Am I forgetting a setting or a property somewhere, or is this perhaps a bug in Data Lake Tools for VS2017?
Do you still have the issue?
I sometimes see this happen if I open an existing solution and the tabs are already open, and I have not yet logged in. I then log in and the drop down menu of the open window will not be refreshed.
I close and reopen the script and it normally shows up.
Another reason, that I think will be addressed soon, could be that you have a filter on your cloud view explorer on which subscriptions you expose. If you hid the subscription there with your ADLA account, you will not see it in the pull down.
In any case, please let us know if you still have the issue and none of the two suggestions help.
I am working on a Continuous Integration project where I need to install update packages in Sitecore instances and roll back the update package if something goes wrong. I am creating the update and rollback update package using Sitecore Courier. I just want to know if there is any mechanism to confirm that my rollback worked correctly i.e. the Sitecore instance has been restored to its previous state.
I don't think you have something out of the box to check if something goes wrong.
I suggest you to create few unit tests using Sitecore FakeDb and check if old
templates still exist, if content is the same,etc
Informations about FakeDb you can find at: https://github.com/sergeyshushlyapin/Sitecore.FakeDb/wiki