I've create the Azure Notebooks library with 'aznbsetup.sh' startup file.
File doesn't run then I open the library, and .aznbsetup.log is not created.
File content is simple
#!/bin/bash
git pull
So I don't know what's happening and how to debug it
After conversation at AzureNotebooks official GH repo, the answer is
Doc is outdated
Log stored in .nb.setup.log (setup log for library), not in aznbsetup.log (doesn't exist anymore)
Related
I'm trying to open this repository using Github Codespaces. Note that this repository is correctly configured for local devcontainer development.
However, when I try to open it in CodeSpaces, it seems to build the container correctly, but fails with:Could not detect any language/platform in the source directory (full log here)
What am I missing?
It looks like you may have run into a regression that Codespaces had during the time specified in your log file.
Given your configuration, Oryx should no longer run, which means you should no longer run into this issue.
Would you mind retrying?
I am trying to create an Azure DevOps extension. As part of this, when I tried to use a npm package azure-pipelines-tasks-azure-arm-rest-v2, it is failing when package extension is done using tfx create extension command showing the following error:
It is because of a license file included in the module in node_modules. When I deleted that file, it created the .vsix file successfully. Is there any alternative for this module? Or Is there a way to exclude a file while using the tfx create extension command?
As the error message indicates, this seems to be happening because of the whitespace in the name of the file OpenSSL License.txt. The easiest way to work around this could be to rename the file before running tfx extension create command.
If that doesn't help, please open an issue with the azure-pipelines-tasks repo. Here is a similar issue opened in the past.
I am trying to set up automatic deployments from my GitLab instance to Azure for the Bot Framework SDK4. I am following this guide.
When I am trying to sync my changes from gitlab to azure I am getting the following error:
Command: deploy.cmd
'deploy.cmd' is not recognized as an internal or external command,
operable program or batch file.
'deploy.cmd' is not recognized as an internal or external command,\r\noperable program or batch file.\r\nD:\Program Files (x86)\SiteExtensions\Kudu\78.11022.3613\bin\Scripts\starter.cmd deploy.cmd
I have tried this on multiple azure instances and I have ran into the error on both. Any idea what could be causing this error?
Sounds like there is something trying to customise your deployment, you should find a .deployment file in your repository. you might have had this if you downloaded the original code from the Azure demo. removing this file from your repository should allow you to sync the code
if you want to restore the .deployment file at a later date the following link from the project kudu repo https://github.com/projectkudu/kudu/wiki/Customizing-deployments should help. You can also download/copy the deploy.cmd file from your Azure directory and add it to your repository
I'm trying to figure out how to run a pre/post command using the deploy.cmd generated by VS/MSBuild. I understand there are pre/postsync commands which can be set on the command line with msbuild but this is fixed within the web deploy package inside of the x.deploy.cmd.
How do I go about customizing the output of this file so that I can run the deploy command with specific parameters?
The intention is a non-developer will pick up the package zip file and import the application into IIS. We use IIS to host some windows services and so to be able to deploy we need to stop and uninstall the service before deployment and then install restart in the post deploy stage.
For certain servers we allow auto deployments from TFS and hook this pre/post command using the .targets file of the msbuild WPP pipeline. However, we want to this to be available to the manual deploy command files.
PreSync/PostSync are features of the msdeploy command line and are not supported by the package/manifest providers, or even the API. They are equivalent to running msdeploy a second time, so there's no way you'll be able to include their functionality while directly importing the package into IIS.
I'd recommend having a batch/powershell file on the server that the user runs after copying the package into the same directory.
The .cmd file that MSBuild generates is boilerplate script that you can simply change to call your pre/post powershell scripts. Just overwrite the one generated by the build with your custom one.
I use Windows 7 and also I use TortoiseSVN to keep track of my code, now I want to migrate my repository to a cloud-service and the requirement is create a *.dump file, but I can't find a way to create it. Some forums say to use "svnadmin" but I can't find it also.
My question is how can I create a *.dump file with TortoiseSVN?
TortoiseSVN ships the svnadmin utility with it. It is a command line utillity. So you will have to create a dump of your repository in the command line.
To create a dump of your repository, use
svnadmin dump C:\SVN\MyProject > C:\tmp\MyProject.dump
where C:\SVN\MyProject is the path to your SVN repo and C:\tmp\MyProject.dump is the path to the dump file, which will be created.
To import your previously made dump file into a new repository, use
svnadmin load C:\SVN\MyProject < C:\tmp\MyProject.dump
where C:\SVN\MyProject is the path to your new SVN repo and C:\tmp\MyProject.dump is the path to the dump file, which should be imported.
Subversion 1.7 now has the svnrdump command line utility.
svnrdump dump https://host/repo > repo.dump
Note that this always creates a dump with deltas, which might not be what you want.
TortoiseSVN is a svn client. It cannot take a dump of your repository. You need a tool like svnadmin on the server hosting your SVN repository to take a dump. You need access to the server and its filesystem.
Also see here for migrating a repository
svnadmin is part of the SVN server, so you should have a direct admin access to your repository server.
The first thing you need to do is follow this tutorial to get some idea about how to use TortoiseSVN on the local machine.
http://www.thinkplexx.com/learn/howto/scm/svn/how-to-create-and-use-local-svn-subversion-repository-on-windows-or-linux-simple-and-fast-step-by-step
once you have done with above tutorial and committed your files to the repository, execute below command.
svnadmin dump TortoiseRepository > dumpfile
If your TortoiseSVN repository is not called 'TortoiseRepository' just change the name above to whatever you have called it. If the dump works you should see lots of '*Dumped revision' messages. The 'dumpfile' now contains an entire export of your TortoiseSVN repository and all the revisions, comments etc.