I have included a custom action in Hotfix with condition "1" so that my custom action will execute in all phases like install, repair and uninstall.
However my custom action is executing only during install and repair phase. It is not executing in uninstall phase.
i have seen logs files. My custom action is logged in install and repair log files. But not logged in uninstall log file(not even showing skipped).
How to execute custom action while uninstalling HotFix.
Below is my custom action:
<InstallExecuteSequence>
<Custom Action="DeleteCATest" Before="InstallFiles">1</Custom>
</InstallExecuteSequence>
<CustomActionRef Id="DeleteCATest"/>
Related
I use Windows Application Packaging Project to generate MSIXBUNDLE for my WPF app.
App installed failed with error message: Windows cannot install package xxxxxx_3.8.3.0_neutral~_hijkl because a different package xxxxxxx_3.8.2.0_neutral~_abcde r with the same name is already installed. Remove package xxxxxx_3.8.2.0_neutral~_abcde before installing. (0x80073cf3)
I think the reason is that I signed the new package (3.8,3) with a new EV code signing certificate. Does WAP tool support option to uninstall previous package? Under the project property tab "Debug" ->"Start option", there is a check box for "Uninstall and then re-install my package. All information about the application state is deleted". But enable it does not seem to do the job.
Thanks,
"Uninstall and then re-install my package. All information about the application state is deleted"
I think this option is useful only for debugging purposes. It sounds like an option to remove a previous copy of the package (that has the same version and product name). So, this does not help with removing older versions.
For MSIX packages, you don't top configure anything specific in the package to trigger the removal of a previous version, as you used to do with an MSI. This is handled automatically by the OS.
But the OS needs to somehow understand which package to remove and I suspect the digital certificate is part of that check. Just manually remove the old version, install the new one, and then build a test version (3.8.4) to confirm if the different certificate was the problem.
I created a Gitlab Ci-CD to remove react and react-dom from devDependencies in package.json when i push my code to master.
but as you can see it says that pipline is passed and job is succeeded but when i look at my master branch react and react-dom are not removed from devDependencies and they are still there.
what should i do with that?
A GitLab CI job doesn't change any of your repository files. It pulls a copy of the repository so that it can run a script, test, etc. against it. If the specified job runs successfully without throwing any errors (exit code), then the job succeeds/passes. You can find a more detailed explanation in the GitLab CI/CD documentation.
If you want to make changes to the repository, you need to have the script run to make the changes, then commit the changes, and push those changes to the repository using the standard git commands.
Just remember that you'll have to authenticate using HTTPS or using SSH.
You'll also likely find this StackOverflow answer on pushing to a GitLab repository through a CI job helpful as well.
I am installing a pipeline, CI/CD a React Project but suddenly it wants me to select an option on my semantic plugin.
How do I force it to install the automatic?
https://prnt.sc/v5ogsf
According to the document: Semantic UI includes an interactive installer to help setup your project. However, we cannot interact with command line task in azure pipelines.
As a workaround, you can complete install Semantic UI step locally.
1.Clone your azure repository to your local.
2.Run npm install semantic-ui command in your project. Please refer to the steps about install Semantic UI in this document.
3.Commit and push the changes to your azure repository.
I was told that a job cannot config the email notification, jenkins says 500 internal server error.
I found out that the problem was about the email-ext plugin. The default Mailer worked fine. Any job using the email-ext plugin cannot save configuration, even no change of the configuration.
I could not find what happens, the jenkins log didn't say anything.
I update the jenkins(2.72, then 2.73), and update all the plugins. problem did not disappear.
I uninstalled the plugin email-ext and tried to reinstall, but then jenkins said 500, so I manually remove the plugin/email-ext/ and the ...email-ext-config.xml, then restart the jenkins.
now any operation with any plugin will return 500 internal server error, even config the job with default mailer.
how could I fix this?
I can no longer add an email-ext post build step to my jenkins jobs.
This worked before, but the I upgraded to jenkins 2.7.1 and the email-ext plugin 2.44.
Now, when I add an post build step to a job and try to save the modified job, I will be taken to a login page and this page will lead to an error and the new step will not be saved.
Frank
One solution is to downgrade your jenkins to earlier working version.
Try uninstall/reinstall of email plugin.
If you are OK with the New version and not willing to downgrade and wanted email as a post build step, follow the below steps.
Steps:
Login to the server where you have installed jenkins and traverse to the that jobs config.xml path.
add the email section to the job's config.xml [You can refer to other existing job's config.xml which contains email section as a post build and use the same in this job, paste those lines in your job's config.xml]
Save you changes.
Now come back to your jenkins GUI and goto manage jenkins section.
Click on "Reload Configuration from Disk", This will reload your changes from server.
You will now be able to find the changes saved.
Another way is to update the job config.xml from jenkins command line.
search for jenkins-cli.jar and you will find a route.